WSFC - Unable to set node weight in Failover cluster
0
votes
0
answers
512
views
I have a two node Windows failover cluster configured with Always on availability groups which are configured for disaster recovery not for high availability. In this windows failover cluster we are not using quorum/witness, in simple terms cluster is set to use of no witness.
We don't want to use quorum because we are having multi subnet cluster configured with AG, By using the quorum configurations for Manual failover given in MSDN we have configured from below URL.
https://learn.microsoft.com/en-us/windows-server/failover-clustering/manage-cluster-quorum#quorum-considerations-for-disaster-recovery-configurations
Current Settings:
No preferred site.
Dynamic Quorum = 1
Node1 is primary and Node Weight(Assigned Vote) =1 and Dynamic Weight(Current Vote) = 0
Node2 is Secondary and Node Weight = 1 and Current Vote = 1
As Node1 is primary I have moved my cluster group resources to Node1 and able to set the node weight property to 1. But while trying to set the Node2 node weight property to 0 it is throwing me an error as below where I am not able to resolve the issue.
Error Message:
Exception setting "NodeWeight": "Unable to save property changes for 'Node2'.
The request is invalid either because node weight cannot be changed while the cluster is in disk-only quorum mode,
or because changing the node weight would violate the minimum cluster quorum requirements"
I have tried to restart the cluster service but didn't fix my error.
I have tried to add a file share quorum witness and then removed still unable to fix the error.
Expected result is:
Node Assigned vote Current Vote
Node1 1 1
Node2 0 0
Quorum type should be: Node Majority
Q1. How to avoid this disk-only quorum situation and fix the error?
Any leads to this error is appreciated.
Asked by info.sqldba
(327 rep)
Oct 11, 2023, 06:47 AM
Last activity: Oct 11, 2023, 09:35 AM
Last activity: Oct 11, 2023, 09:35 AM