[Info-vax] set cluster/expected_votes

[JF Mezei]

Malcolm Dunnett wrote:

>   What it does is tells the other nodes to recompute quorum based on the
> votes remaining in the cluster. I don't know if you consider this "much" 
> or not, but it would seem to be precisely what is needed in this situation.

It won't magically allow a cluster to continue to operate with fewer
nodes than it had been designed to operate. AKA: you cannot cheat the
minimums set by the sysgen expected_votes if I remember correctly.

I went through this when I moved from MV-II and 3100 to having
VAX-4000-600, VAX 4000-200, 3100, with the -600 and -200 going into the
cabinet where the MVII used to be. I had to judicioulsy set the expected
votes to allow the remove_node function to work properly. It wasn't just
 physical moves, but also giving the 4000-600 the same SCS node name as
the MV-II and that required successive rebootes of each node to make it
forget it ever know about the microvax II, and allow the 4000-600 to
change it name from a temporary name to its permanent name.

And yes, I managed to maintain the cluster uptime through this.