• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 233
  • Last Modified:

Cluster name taking a long time to become online....

I am using the "change group" function on the cluster administrator... it takes quite a long time for "Cluster Name" to get back online.

Any reason this might be?

I can wipe the boxes if need be, but I'd like to understand the reasoning for the problem first! :)

Thanks!
0
overworkedops
Asked:
overworkedops
  • 6
  • 3
  • 2
  • +1
1 Solution
 
overworkedopsAuthor Commented:
Oh and to quantify, a "Long time", it's like 3 minutes or so.

Thanks again!
0
 
DireOrbAntCommented:
How many instances in the cluster? Is it active/passive?
change group will make the node failover to the other one, swaping the resources over.
If the required memory is high or if long transactions needs to be rolled forward or backwards, it can increase the time taken.
The SQL service should restart in less than a minute most times (if failed by hand), asside from transactions.
0
 
overworkedopsAuthor Commented:
Single instance, active/passive. I'm going to wipe and see what happens... I'm sure it will fix it.
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
overworkedopsAuthor Commented:
Okay, I've wiped... no fix. The cluster name is still taking a long time to fail over. I wiped EVERYTHING -- this is a cluster that's set up from scratch. Any ideas what it might be? I am thinking something on the domain controller, but I'm not sure.
0
 
NightmanCTOCommented:
What is the load like? If any?
0
 
overworkedopsAuthor Commented:
None... there's nothing on the box except SP1 and the cluster services.

I think it's a DNS issue, but I only find 1 entry for the cluster in DNS and I deleted that before I rebuilt... just weird :\
0
 
NightmanCTOCommented:
Available memory on each node?
Any load on the SAN?
0
 
overworkedopsAuthor Commented:
8 GB of RAM, plenty free... it's not a SAN, just DAS, an HP msa 500, using the shared bus.

Mind you, the disk group fails over perfectly and fast, so does the cluster IP... just the cluster name takes a long time.
0
 
NightmanCTOCommented:
Have a look in the SQL server logs to see the sequence of events - perhaps they will indicate a particular process that is taking time.
0
 
overworkedopsAuthor Commented:
It was reverse DNS... works fine now :)
0
 
DireOrbAntCommented:
Cool :)
0
 
Computer101Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 6
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now