[ClusterLabs] Antw: Re: Antw: [EXT] Coming in Pacemaker 2.1.2: new fencing configuration options

[Andrei Borzenkov]

On Mon, Oct 11, 2021 at 9:29 AM Ulrich Windl
<Ulrich.Windl at rz.uni-regensburg.de> wrote:
....
> >> Also how long would such a delay be: Long enough until the other node
> >> is
> >> fenced, or long enough until the other node was fenced, booted
> >> (assuming it
> >> does) and is running pacemaker?
> >
> > The delay should be on the less-preferred node, long enough for that
> > node to get fenced. The other node, with no delay, will fence it if it
> > can. If the other node is for whatever reason unable to fence, the node
> > with the delay will fence it after the delay.
>
> So the "fence intention" will be lost when the node is being fenced?
> Otherwise the surviving node would have to clean up the "fence intention".
> Or does it mean the "fence intention" does not make it to the CIB and stays
> local on the node?
>

Two nodes cannot communicate with each other so the surviving node is
not aware of anything the fenced node did or intended to do. When the
fenced node reboots and pacemaker starts it should pull CIB from the
surviving node, so whatever intentions the fenced node had before
reboot should be lost at this point.