[ClusterLabs] Antw: corosync taking almost 30 secs to detect node failure in case of kernel panic

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Wed Jan 10 02:32:16 EST 2018


Maybe define "detecting node failure". Culkd it be your 30 seconds are between detection and reaction? Logs would help here, too.


>>> ashutosh tiwari <ashutosh.kvas at gmail.com> schrieb am 10.01.2018 um 08:13 in
<CA+vEgjiKG_VGegT7Q+wCqn6merFNrvegiQs+RHRuxzE=muVb3Q at mail.gmail.com>:
> Hi,
> We have two node cluster running in active/standby mode and having IPMI
> fencing configured.
> In case of kernel panic at Active node, standby node is detecting node
> failure in around 30 secs which leads to delay in standby node taking the
> active role.
> we have totem token timeout as 10000 msecs.
> Please let us know in case there is any more configuration controlling
> membership detection.
> s/w versions.
> centos 6.7
> corosync-1.4.7-5.el6.x86_64
> pacemaker-1.1.14-8.el6.x86_64
> Thanks and Regards,
> Ashutosh Tiwari

More information about the Users mailing list