How can we determine why corosync was not scheduled, causing an eviction?

Solution Verified - Updated -

Issue

  • A token loss event was observed around the time of a "Corosync main process was not scheduled for X ms" message.
Dec 15 00:10:39 node42 corosync[33376]:   [TOTEM ] Process pause detected for 14709 ms, flushing membership messages.
Dec 15 00:10:39 node42 corosync[33376]:   [MAIN  ] Corosync main process was not scheduled for 14709.0010 ms (threshold is 8000.0000 ms). Consider token timeout increase.

Environment

  • Red Hat Enterprise Linux 7, 8 (with the High Availability Add On)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In