[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
arvidjaar at gmail.com
Tue Sep 3 23:59:54 EDT 2019
04.09.2019 0:27, wferi at niif.hu пишет:
> Jeevan Patnaik <g1patnaik at gmail.com> writes:
>>  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*.
Can you elaborate? This is the first time I see that corosync has
anything to do with watchdog. How exactly corosync interacts with
watchdog? Where in corosync configuration watchdog device is defined?
More information about the Users