March 10, 2017 at 8:01 am
hi,
I have 2 nodes running AlwaysOn availability groups. When node 1 is primary and I brute force shutdown node 2, then node 1 goes into resolving state, and databases are not longer accessible.
However if I am running primary on node 2 and brute force shutdown node 1, then everything seems to work.
Both are configured with listener, synchronous commit and automatic failover.
Could this be because of those settings ?
March 10, 2017 at 8:07 am
What is happening in your Windows cluster and quorum when you perform the shutdown?
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
March 10, 2017 at 9:23 am
oskargunn - Friday, March 10, 2017 8:01 AMhi,I have 2 nodes running AlwaysOn availability groups. When node 1 is primary and I brute force shutdown node 2, then node 1 goes into resolving state, and databases are not longer accessible.
However if I am running primary on node 2 and brute force shutdown node 1, then everything seems to work.Both are configured with listener, synchronous commit and automatic failover.
Could this be because of those settings ?
Can you post details of any errors from the cluster events and the sql error log.
can you provide detail on the cluster setup, including node count and placement and quorum configuration.
At a guess i would say you're using a disk witness attached to the one node
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply