When adding a new node to an existing failover cluster it becomes a possible owner and takes ownership

Question

Hello.

Apologies if this is not the correct place for this.

I have a WSFC that has multiple nodes which have SQL Server 2016 SP2 installed on them. We are running Windows Server 2016 Datacenter.

When I add a new node to the cluster it automatically becomes a "possible owner" and immediately the cluster tries to make it the "Current Host Server". We do not want to to become a possible owner or the "Current Host Server".

Is there a way to add a node without this happening?

Thank you.

Thread source link: https://social.technet.microsoft.com/Forums/windowsserver/en-US/7c752504-5c01-4a51-b69d-3a41c77f32fb/when-adding-a-new-node-to-an-existing-failover-cluster-it-becomes-a-possible-owner-and-takes?forum=winserverClustering

Answer 1

Hi,

1. If the "Current Host Server" move to the new added node and you would like to change it, we may use "Move Core Cluster Resources" > "Select Node" to move back to the node we like.
2. For the Cluster role, we may set the "Possible Owners" in the role>"Resources":
3. Although we could move back the role or "Current Host Server" to dedicated node, your issue seems strange. Generally, the roles or cluster will failover just when the current owner node is down or other reasons can't hold the role running. Such as patching. Then, please check if the Cluster nodes are all running well:

a. Please try to run Cluster Validation at a maintenance time, check if there's error in the report.

b. Please check the Cluster event log in Event log or filter the System log with Failover cluster to check if there's any error message when adding the cluster node.

Thanks for your time!

Best Regards,

Anne