On 01/27/2014 04:08 PM, Vivek Goyal wrote:
IIUC, you are saying that there are two timeouts in effect. One says
that
every 60 seconds a message should be received from fence_kdump. And other
timeout is global upper limit set by cluster admin and dump should finish
in that time.
Yes, you are right.
So first tick based fence_kdump timeout should not be a problem.
Only
problem will be this absolute upper limit timeout for cluster. I am
curious to know what's the default value for this timeout.
The default value
for this is 60 seconds (variable pcmk_reboot_time)
source:
http://clusterlabs.org/man/stonithd.7.html
m,