AlwaysOn SQL 2014 Windows failover Cluster issues

Posted on 2016-09-12
Last Modified: 2016-09-23
Hi Experts, We have upgraded SQL Server 2014 Alwayson and we are getting issues on cluster sudden failures. the cluster fail-over happening suddenly and getting resolved automatically after sometime. please see the below cluster event error messages and guide me how can I resolve those issues.

1.      Cluster node 'ABC' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
2.      File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\xyz20p\srv23pQuorum$'. Please ensure that file share '\\xyz20p\srv23pQuorum$' exists and is accessible by the cluster.
3.      Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed. Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Question by:tschary
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
LVL 40

Expert Comment

ID: 41794513
I assume you have left the default heartbeat and if the share where the quorum sits is "unavailable" for any reason for more than the heartbeat interval your cluster will automatically fail-over so you have 2 options - 1 good and 2 not so good but on some slower networks/connections to SAN you may have no choice:

1. make sure the share where quorum sits is 100% up no matter what
2. increase the heartbeat interval from default to a value that suits your connections.
LVL 50

Expert Comment

by:Vitor Montalvão
ID: 41795512
Are you using a network share as Quorum?

Author Comment

ID: 41795537
Hi Vitor, Yes. we are using network share as quorum. please help me and provide any more solutions.
Why You Need a DevOps Toolchain

IT needs to deliver services with more agility and velocity. IT must roll out application features and innovations faster to keep up with customer demands, which is where a DevOps toolchain steps in. View the infographic to see why you need a DevOps toolchain.

LVL 50

Expert Comment

by:Vitor Montalvão
ID: 41795556
I never used a network share for Quorum and can't help you much with this.
Just know that if the share is down then the Quorum won't be available. You should check first for the availability of the share.
Also know that the network share shouldn't reside in any of the cluster nodes. Hopefully is not your case.

Author Comment

ID: 41795576
Hi Vitor, Network share not reside in any cluster node. It is a separate server. Please let me know What are the best practices for quorum in this case.
LVL 50

Expert Comment

by:Vitor Montalvão
ID: 41795717
I usually use a SAN storage. I know that also works with a network share but besides the two validations I wrote above I don't have any expertise working with these kind of quorum.
LVL 40

Accepted Solution

lcohan earned 500 total points
ID: 41796067
Did you had a look at the recommendations at the link I posted just because you have a "share" that looks like is not that reliable for whatever reason?

In particular did you read about:
Relaxed Monitoring – Provides more forgiving failure detection which provides greater tolerance of brief transient network issues.  These longer time-outs will result in cluster recovery from hard failures taking more time and increasing downtime.
I believe you should try that first and increase as suggested "with moderation" the SameSubnetThreshold to 15 or 20.

Author Comment

ID: 41796078
Thanks lcohan. Sure I wil go through your recommendations and implement it. will get back to you soon.

Author Closing Comment

ID: 41812562
We have found another solution either net adapter issues and changed those  settings. Also heartbeat setting helped us.

Featured Post

Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes.  We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question