Hi,

For testing purposes one of our nodes was put in standby node and then 
rebooted several times. When the standby node started up, it joined the 
cluster as a new member and it resulted in transitions between the online 
nodes. However, when the standby node was rebooted in mid-transitions, it 
triggered another transitions again. As a result, live migrations was 
aborted and guests stopped/started.

How can one make sure that join/leave operations of standby nodes do not 
affect the location of the running resources?

It's pacemaker 1.1.16-1 with corosync 2.4.2-3+deb9u1 on debian stretch 
nodes.

Best regards,
Jozsef
--
E-mail : kadlecsik.joz...@wigner.mta.hu
PGP key: http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address: Wigner Research Centre for Physics, Hungarian Academy of Sciences
         H-1525 Budapest 114, POB. 49, Hungary
_______________________________________________
Users mailing list: Users@clusterlabs.org
https://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to