[ClusterLabs] Stopping all nodes causes servers to migrate
hunter86_bg at yahoo.com
Sun Jan 24 23:48:46 EST 2021
I think that it makes sense, as '--all' should mean 'reach all servers and shutdown there'.Yet, when you run 'pcs cluster stop' - the migration of the resources is the only option.
Still, it sounds like a bug.
Best Regards,Strahil Nikolov
Sent from Yahoo Mail on Android
On Sun, Jan 24, 2021 at 22:31, Digimer<lists at alteeve.ca> wrote: Hi all,
Right off the bat; I'm using a custom RA so this behaviour might be a
bug in my agent.
I had a test server (srv01-test) running on node 1 (el8-a01n01), and on
node 2 (el8-a01n02) I ran 'pcs cluster stop --all'.
It appears like pacemaker asked the VM to migrate to node 2 instead of
stopping it. Once the server was on node 2, I couldn't use 'pcs resource
disable <vm>' as it returned that that resource was unmanaged, and the
cluster shut down was hung. When I directly stopped the VM and then did
a 'pcs resource cleanup', the cluster shutdown completed.
In my agent, I noted these environment variables had been set;
OCF_RESKEY_name = srv01-test
OCF_RESKEY_CRM_meta_migrate_source = el8-a01n01
OCF_RESKEY_CRM_meta_migrate_target = el8-a01n02
OCF_RESKEY_CRM_meta_on_node = el8-a01n01
So as best as I can tell, pacemaker really did ask for a migration. Is
this the case? If not, what environment variables should have been set
in this scenario?
Thanks for any insight!
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
Manage your subscription:
ClusterLabs home: https://www.clusterlabs.org/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users