April 14, 2014 at 8:02 pm
I have a active passive cluster.I see the following errors before the sql server got restarted on the same node.
Event ID: 19019
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
[sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][SQL Server Native Client 10.0]Query timeout expired
[sqsrvres] OnlineThread: QP is not online.
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
[sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][SQL Server Native Client 10.0]Query timeout expired
[sqsrvres] OnlineThread: QP is not online.
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
[sqsrvres] printODBCError: sqlstate = HYT00; native error = 0;
message = [Microsoft][SQL Server Native Client 10.0]Query timeout expired
[sqsrvres] OnlineThread: QP is not online.
In sql server error logs the following messages appeared before the sql service failed--
New queries assigned to process on Node 1 have not been picked up by a worker thread in the last 120 seconds.
The client was unable to reuse a session with SPID 4433, which had been reset for connection pooling.
All the above errors happened around 7:17 p.m and the sql service got restarted at 7:25 p.m.
We also had a sql deadlock stack dump created before these messages. I am not able to figure out what exactly the problem is? Any help would be appreciated ?
Thanks,
April 14, 2014 at 8:46 pm
what is returned by @@version?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 14, 2014 at 9:04 pm
Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64)
Copyright (c) 1988-2008 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
April 15, 2014 at 8:07 am
Any suggestions??
April 15, 2014 at 8:13 am
Good you have the latest sp.
The qp may have been offline for those errors because the service was trying to transition from one node to another. The reason it stayed on the same node may be that the server has a restriction prohibiting failover to a different node.
Could you verify there are no failover rules that would prevent it from failing over to the other node?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 15, 2014 at 9:04 am
If resource fails attempt to restart on the same node setting is on. I guess it's default setting. We are working with msft team and changed few tcp chimney settings and updated the hp driver updates etc. This happens in a day or two after manual failover of the services.It looks like it's a known issue.
http://www.sqlservercentral.com/Forums/Topic399630-149-1.aspx
April 16, 2014 at 7:56 am
any more suggestions??
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply