Failover Cluster Primary Nodes Current Vote = 0
I currently have a SQL 2016 Always On Availability Group. I have two nodes in the failover cluster both Server 2012 R2 boxes with a File Share Witness as my domain controller. The problem I am running into is when I look at my two nodes in the cluster it shows the primary node as Current Vote of 0. My other node has a Current Vote of 1. Both nodes have an assigned vote only one has a current vote. I then have my File Share Witness.
The issue is last night due to updates my file share witness rebooted and witht he primary node having no vote it caused my cluster to fail. Once the file share came back online the clustered was fixed
So my questions are what would cause the node to lose its voting rights and how can I get it back.
The issue is last night due to updates my file share witness rebooted and witht he primary node having no vote it caused my cluster to fail. Once the file share came back online the clustered was fixed
So my questions are what would cause the node to lose its voting rights and how can I get it back.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The only way I know for it to change is for someone to reconfigure it. That said, it could be something just glitched.
ASKER
These helped me as I just reassigned the voting and all is fine now.
ASKER