25.01.2012 10:58, Jan Friesse wrote: > Dne 25.1.2012 06:19, Fabio M. Di Nitto napsal(a): >> On 01/24/2012 09:09 PM, Vladislav Bogdanov wrote: >>> 24.01.2012 19:10, Fabio M. Di Nitto wrote: >>> [snip] >>>>> If I power on more "unseen" nodes, expected_votes is automatically >>>>> incremented and saved into CIB. If I then power down that nodes, their >>>>> votes are still considered until I remove them from CIB and decrement >>>>> expected_votes manually (actually that part didn't fully work last >>>>> time >>>>> I checked). >>>> >>>> You can do this with votequorum already. New nodes are added to the >>>> list >>>> and expected_votes increases automagically. On removal, you will >>>> need to >>>> manually decrement expected_votes as you do now pretty much. >>> >>> BTW, is it now possible to alter nodelist at runtime (remove some nodes >>> from there)? It is kinda problematic with flatiron. >> >> I believe so, but Honza has been working on that portion of the code and >> should be able to answer details better. The quorum module itself tracks >> changes in that list and recalculate etc. >> > > Ya, it's perfectly possible. Just create nodelist.node.X.ring0_addr, > where X is even nonexisting number for adding new node, or existing for > change the node (doesn't work for local node, because we are not > supporting rebind of socket yet). You can also (for example) alter > number of votes by setting nodelist.node.X.quorum_votes. > > So let's give example: > - Let's add node with address 192.168.1.5 > corosync-cmapctl -s nodelist.node.5.ring0_addr str 192.168.1.5 > > Corosync log should show something like (in debug mode): > adding dynamic member 192.168.1.5 for ring 0 > > - Now let's change newly added node number of votes: > corosync-cmapctl -s nodelist.node.5.quorum_votes u32 3 > > - And now remove node: > corosync-cmapctl -d nodelist.node.5.ring0_addr > Great. That all is to be done only on one node, correct? Is it also possible to just reload corosync config on one node to apply new configuration to a whole cluster? Vladislav _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
