Andrei Maruha <andrei_mar...@epam.com> writes: > Hi, > Attached patch contains a little bit reworked function next_nodeid, > because some times it is not clear why node gets new id during rejoin > operation. Ex: > 1. cluster with one node, id is 1; > 2. join another node, joined node gets id 2; > 3. delete the node with id 1 from the cluster; > 4. join this node again and ... joined node gets id 3. > > With this fix node id for the first node after rejoin will be set again > to 1. >
Hi, Thank you for this patch! I have integrated it upstream in this commit: https://github.com/ClusterLabs/crmsh/commit/7f418f19 It will be included in the next release on the 2.2 branch. I modified the patch slightly to avoid adding a dependency on the mock library. Cheers, Kristoffer > Best Regards, > Andrei Maruha > -- // Kristoffer Grönlund // kgronl...@suse.com _______________________________________________ Users mailing list: Users@clusterlabs.org http://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
