| Groups | Blog | Home |
sql server clustering : Clustering Service not starting right away on One Node
service on one of the nodes doesn't start up right away. I have checked the services to make sure that it is set to automatic which it is. Both nodes are current with the latest patches and security updates. I'm a little clueless as to why this is happening. Here is the real weird part after 1 minute the cluster service starts on the node that is giving me troubles.
Hi
If you do a fail-over using cluster admin, are there any resources (that SQL server depends on) take a long to come online? I have seen similar issues when the devices take long to come online due to high SAN activity. Does the SQL Server resource come online, but take a long time until it has done it's recovery steps? This can occur when the other node was de-porting it's devices and still had IO pending. This results in not all pages being fluished to SAN, so SQL Server has to do more recovery on the database start-up. The best guage of how quickly a resource comes online is to look at cluster admin during the failover. Regards Mike Regards Mike [quoted text, click to view] "Thomas" wrote:
> I just set up a cluster attached to a SAN. I have had it where the cluster > service on one of the nodes doesn't start up right away. I have checked the > services to make sure that it is set to automatic which it is. Both nodes > are current with the latest patches and security updates. I'm a little > clueless as to why this is happening. Here is the real weird part after 1 > minute the cluster service starts on the node that is giving me troubles.
We haven't installed SQL server yet. I should've posted that first. But I
know from passed installs that SQL does take some time to come online. The SAN doesn't have much activity on it right now [quoted text, click to view] "Mike Epprecht (SQL MVP)" wrote:
> Hi > > If you do a fail-over using cluster admin, are there any resources (that SQL > server depends on) take a long to come online? > I have seen similar issues when the devices take long to come online due to > high SAN activity. > > Does the SQL Server resource come online, but take a long time until it has > done it's recovery steps? > This can occur when the other node was de-porting it's devices and still had > IO pending. This results in not all pages being fluished to SAN, so SQL > Server has to do more recovery on the database start-up. > > The best guage of how quickly a resource comes online is to look at cluster > admin during the failover. > > Regards > Mike > Regards > Mike > > "Thomas" wrote: > > > I just set up a cluster attached to a SAN. I have had it where the cluster > > service on one of the nodes doesn't start up right away. I have checked the > > services to make sure that it is set to automatic which it is. Both nodes > > are current with the latest patches and security updates. I'm a little > > clueless as to why this is happening. Here is the real weird part after 1 > > minute the cluster service starts on the node that is giving me troubles.
Hi
Have a look in your event logs and check the time differences between when Node A shuts down and Node B notices it and starts up. There will be at least 15 event messages during this process. Post the information here so that I can compare it to our big clusters. Regards Mike [quoted text, click to view] "Thomas" wrote:
> We haven't installed SQL server yet. I should've posted that first. But I > know from passed installs that SQL does take some time to come online. The > SAN doesn't have much activity on it right now > > "Mike Epprecht (SQL MVP)" wrote: > > > Hi > > > > If you do a fail-over using cluster admin, are there any resources (that SQL > > server depends on) take a long to come online? > > I have seen similar issues when the devices take long to come online due to > > high SAN activity. > > > > Does the SQL Server resource come online, but take a long time until it has > > done it's recovery steps? > > This can occur when the other node was de-porting it's devices and still had > > IO pending. This results in not all pages being fluished to SAN, so SQL > > Server has to do more recovery on the database start-up. > > > > The best guage of how quickly a resource comes online is to look at cluster > > admin during the failover. > > > > Regards > > Mike > > Regards > > Mike > > > > "Thomas" wrote: > > > > > I just set up a cluster attached to a SAN. I have had it where the cluster > > > service on one of the nodes doesn't start up right away. I have checked the > > > services to make sure that it is set to automatic which it is. Both nodes > > > are current with the latest patches and security updates. I'm a little > > > clueless as to why this is happening. Here is the real weird part after 1 > > > minute the cluster service starts on the node that is giving me troubles.
Node 2 which I haven't seen the problem with having ownership of the cluster.
When I reboot node 1 is when I see the problem of it taking 1 mintue to start the cluster service. [quoted text, click to view] "Geoff N. Hiten" wrote:
> That may be somewhat normal on a simultaneous startup. The first node grabs > the quorum device and owns the cluster but isn't talking on the network yet. > The second node tries to get the device but times out. Eventually the > service comes online and talks to the other node and agrees on who is in > charge. This is especially prevalent on SCSI-based clusters. > > Check the System and Application event logs on both systems to see if there > are any unusual startup errors. Also, check what happens when the second > node is rebooted. If the cluster service does come online quickly, it is > just a device contention issue. I try and avoid powering up more than one > cluster node at a time. > > > -- > Geoff N. Hiten > Microsoft SQL Server MVP > Senior Database Administrator > Careerbuilder.com > > I support the Professional Association for SQL Server > www.sqlpass.org > > "Thomas" <Thomas@discussions.microsoft.com> wrote in message > news:AF61883D-AE50-4F3F-AD3F-3F07834A2B78@microsoft.com... > > I just set up a cluster attached to a SAN. I have had it where the > cluster > > service on one of the nodes doesn't start up right away. I have checked > the > > services to make sure that it is set to automatic which it is. Both nodes > > are current with the latest patches and security updates. I'm a little > > clueless as to why this is happening. Here is the real weird part after 1 > > minute the cluster service starts on the node that is giving me troubles. > > The other node is perfectly fine. > >
That may be somewhat normal on a simultaneous startup. The first node grabs
the quorum device and owns the cluster but isn't talking on the network yet. The second node tries to get the device but times out. Eventually the service comes online and talks to the other node and agrees on who is in charge. This is especially prevalent on SCSI-based clusters. Check the System and Application event logs on both systems to see if there are any unusual startup errors. Also, check what happens when the second node is rebooted. If the cluster service does come online quickly, it is just a device contention issue. I try and avoid powering up more than one cluster node at a time. -- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org [quoted text, click to view] "Thomas" <Thomas@discussions.microsoft.com> wrote in message news:AF61883D-AE50-4F3F-AD3F-3F07834A2B78@microsoft.com... > I just set up a cluster attached to a SAN. I have had it where the cluster > service on one of the nodes doesn't start up right away. I have checked the > services to make sure that it is set to automatic which it is. Both nodes > are current with the latest patches and security updates. I'm a little > clueless as to why this is happening. Here is the real weird part after 1 > minute the cluster service starts on the node that is giving me troubles. > The other node is perfectly fine.
Node order is arbitrary in a cluster. We could use Node X and Node Y
instead of Node 1 and Node 2. Try manually stopping and starting the cluster service on Node 1. If it restarts quickly, then the problem likely is one of the services that the cluster service depends on. Time service is a usual suspect for that, but you will have to check the entire list. Again, the Application and System event logs are your friends here. Now is the time to deal with this issue, not after you load SQL and get this baby into production. -- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org [quoted text, click to view] "Thomas" <Thomas@discussions.microsoft.com> wrote in message news:29B2402A-537B-4DCE-A137-FA200DD28872@microsoft.com... > Node 2 which I haven't seen the problem with having ownership of the cluster. > When I reboot node 1 is when I see the problem of it taking 1 mintue to > start the cluster service. > > "Geoff N. Hiten" wrote: > > > That may be somewhat normal on a simultaneous startup. The first node grabs > > the quorum device and owns the cluster but isn't talking on the network yet. > > The second node tries to get the device but times out. Eventually the > > service comes online and talks to the other node and agrees on who is in > > charge. This is especially prevalent on SCSI-based clusters. > > > > Check the System and Application event logs on both systems to see if there > > are any unusual startup errors. Also, check what happens when the second > > node is rebooted. If the cluster service does come online quickly, it is > > just a device contention issue. I try and avoid powering up more than one > > cluster node at a time. > > > > > > -- > > Geoff N. Hiten > > Microsoft SQL Server MVP > > Senior Database Administrator > > Careerbuilder.com > > > > I support the Professional Association for SQL Server > > www.sqlpass.org > > > > "Thomas" <Thomas@discussions.microsoft.com> wrote in message > > news:AF61883D-AE50-4F3F-AD3F-3F07834A2B78@microsoft.com... > > > I just set up a cluster attached to a SAN. I have had it where the > > cluster > > > service on one of the nodes doesn't start up right away. I have checked > > the > > > services to make sure that it is set to automatic which it is. Both nodes > > > are current with the latest patches and security updates. I'm a little > > > clueless as to why this is happening. Here is the real weird part after 1 > > > minute the cluster service starts on the node that is giving me troubles. > > > The other node is perfectly fine. > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |