[ClusterLabs] Antw: Timeout before fencing/stonith happens

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Wed Sep 2 02:47:18 EDT 2015


In my experience I/O delays (caused by big I/O loads) cause all types of monitor operations to exceed their expected timeouts, even where you don't expect it. We had monitor timeouts for the network interface (despite of LVM) on big loads.
So follow your logs and increase your affected timeouts.


>>> "Nicolas S." <lists at tropicdreams.net> schrieb am 02.09.2015 um 08:14 in
Nachricht <033a9a78c040c654f5135ae1b7abd810 at atoll.tropicdreams.net>:
> Hello,
> I write this mailing-list because I'm having a little trouble with my 
> cluster.
> I'm running a 3 node centos 7 cluster. Resource/stonith and all is 
> configured.
> Since a couple of days my backups take a little bit more time and one node 
> is getting high load. At a certain point it's fenced by the other nodes.
> Of course I'm thinking of correcting that backup issue but for the moment 
> it's not done.
> I tried to find in the docs a general property to make the nodes to wait a 
> little bit more before fencing the node, but i didn't really found it (or I 
> misread docs). It seems that the stonith-timeout isn't the solutiion.
> Is there a best practice or such property ?
> Thanks to all.
> Regards,
> Nicolas.

More information about the Users mailing list