[Info-vax] set cluster/expected_votes

[norm.raphael at metso.com]

Malcolm Dunnett wrote on 08/12/2009 03:21:11 PM:

> Malcolm Dunnett wrote:
> 
> > 
> > Sure you can, use the REMOVE_NODE option of SYS$SYSTEM:SHUTDOWN.COM 
when 
> > you shut down the no longer wanted 2 vote member.
> > 
> > (google for OPC$REMOVE_NODE if you want more information, that is the 
> > mechanism that SHUTDOWN.COM uses)
> 
> OK, a little more research suggests we are both right :-)
> 
> In earlier versions of VMS, SHUTDOWN.COM used the SET 
> CLUSTER/EXPECTED_VOTES mechanism to remove a node. This mechanism does 
> not work for removing the "second to last voting member" from the 
> cluster ( as suggested earlier in this thread). It's a race condition 
> type of thing - the node going down is still contributing votes at the 
> time the command is executed so its votes apply towards the quorum and 
> prevent it from being lowered.
> 
> Current versions of VMS use OPC$REMOVE_NODE which removes this 
> limitation. I'm not sure when this changed (VMS 8.0?).

Works on my V7.3-2 cluster.
                                                         I believe this 
> essentially renders the SET CLUSTER/EXPECTED_VOTES mechanism redundant.
> 
> If Hoff still follows this group perhaps he could jump in and tell us 
> the whole story?
> 
> See: http://tinyurl.com/vmsmgmtguide for more gory details on the old 
> method.
>