[ClusterLabs] Corosync main process was not scheduled for 2889.8477 ms (threshold is 800.0000 ms), though it runs with realtime priority and there was not much load on the node

[wferi at niif.hu]

Jeevan Patnaik <g1patnaik at gmail.com> writes:

> [16187] node1 corosyncwarning [MAIN  ] Corosync main process was not
> scheduled for 2889.8477 ms (threshold is 800.0000 ms). Consider token
> timeout increase.
> [...]
> 2. How to fix this? We have not much load on the nodes, the corosync is
> already running with RT priority.

Does your corosync daemon use a watchdog device?  (See in the startup
logs.)  Watchdog interaction can be *slow*.
-- 
Feri