[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
jfriesse at redhat.com
Mon Sep 2 08:20:29 EDT 2019
Jeevan Patnaik napsal(a):
> Also, both are physical machines.
> On Fri, Aug 30, 2019 at 7:23 PM Jeevan Patnaik <g1patnaik at gmail.com> wrote:
>> We see the following messages almost everyday in our 2 node cluster and
>> resources gets migrated when it happens:
>>  node1 corosyncwarning [MAIN ] Corosync main process was not scheduled for 2889.8477 ms (threshold is 800.0000 ms). Consider token timeout increase.
>>  node1 corosyncnotice [TOTEM ] c.
>>  node1 corosyncnotice [TOTEM ] A new membership (192.168.0.1:1268) was formed. Members joined: 2 left: 2
>>  node1 corosyncnotice [TOTEM ] Failed to receive the leave message. failed: 2
>> After setting the token timeout to 6000ms, at least the "Failed to
>> receive the leave message" doesn't appear anymore. But we see corosync
>> timeout errors:
>>  node1 corosyncwarning [MAIN ] Corosync main process was not
>> scheduled for 6660.9043 ms (threshold is 4800.0000 ms). Consider token
>> timeout increase.
>> 1. Why is the set timeout not in effect? It's 4800ms instead of 6000ms.
It is in effect. Threshold for pause detector is set as 0.8 * token timeout.
>> 2. How to fix this? We have not much load on the nodes, the corosync is
>> already running with RT priority.
There must be something wrong. If you increase token timeout even higher
(let's say 12sec) is it still appearing or not? If so, isn't the machine
swapping (for example) or waiting for IO? If you try to run it without
RT priority, does it help?
>> The following is the details of OS and packages:
>> Kernel: 3.10.0-957.el7.x86_64
>> OS: Oracle Linux Server 7.6
>> Thanks in advance.
>> Create your own email signature
> Manage your subscription:
> ClusterLabs home: https://www.clusterlabs.org/
More information about the Users