[Pacemaker] Resource fails to stop

[Arnold Krille]

On Thursday 26 July 2012 12:43:20 Andrew Widdersheim wrote:
> One of my resources failed to stop due to it hitting the timeout setting.
> The resource went into a failed state and froze the cluster until I
> manually fixed the problem. My question is what is pacemaker's default
> action when it encounters a stop failure and STONITH is not enabled? Is it
> what I saw where the resource goes into a failed state and doesn't try to
> start it anywhere until manual intervention or does it continually try to
> stop it?
> 
> The reason I ask is I found the following link which suggests to me that
> after the failure timeout is reached when stopping a resource and STONITH
> is not enabled pacemaker will continually try to stop the resource until it
> succeeds:

Without fencing configured, there are two ways the cluster can react:
 - Wait till some manual fencing and fixing happens.
 - Ignore the missing fencing.
By default pacemaker tends to do the first (aka it fences, has no active 
fencing resources but still waits until the normal state is restored) unless 
you also set the option to ignore/disable fencing. Which is not recommended in 
production.

Have fun,

Arnold
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120726/10a51d44/attachment-0004.sig>