[ClusterLabs] Q: Migration before fencing?

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Fri Aug 6 08:53:13 EDT 2021


I had this unecxpected behavior this morning:
A VM resource failed to stop and the cluster node (hypervisor) was fenced.
However there were VMs runninf that could have been live-migrated.
That wasn't even tried.

On another occasion when multiple VMs were to be live-migrated and one failed,
I thought the cluster would wait for the migrations to finish before issuing the fence command.

So a few questions:
Is it intended that no migrations are attempted before fencing a node?
If so, is there a way to make the cluster attempt migration before fencing?
Is it true that the cluster will delay fencing while there are outstanding (no finished) operations?

OS being used is SLES15 SP2 (pacemaker version 2.0.4+20200616.2deceaa3a-3.9.1-2.0.4+20200616.2deceaa3a, corosync-2.4.5-6.3.2.x86_64, resource-agents-4.4.0+git57.70549516-3.23.1.x86_64)


More information about the Users mailing list