Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««123»»

cluster failover --memory Expand / Collapse
Author
Message
Posted Friday, March 7, 2014 1:55 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 2:21 PM
Points: 391, Visits: 1,937
Yes Perry is right. I mean DBCC DROPCLEANBUFFERS. Edited the previous post.
Post #1548892
Posted Saturday, March 8, 2014 12:07 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:26 PM
Points: 6,300, Visits: 13,580
muthyala_51 (3/7/2014)
Yes Perry is right. I mean DBCC DROPCLEANBUFFERS. Edited the previous post.

You need to checkpoint the database(s) before dropping clean buffers. Did you run checkpoint first?


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1548950
Posted Saturday, March 8, 2014 5:12 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 2:21 PM
Points: 391, Visits: 1,937
Nope. I never ran the checkpoint stmnt.
Post #1548958
Posted Saturday, March 8, 2014 6:43 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 2:21 PM
Points: 391, Visits: 1,937
any suggestions?
Post #1549016
Posted Sunday, March 9, 2014 3:33 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 1:26 PM
Points: 6,300, Visits: 13,580
muthyala_51 (3/8/2014)
any suggestions?

For what?
anything now would just be speculation since the instance was restarted


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1549038
Posted Sunday, March 9, 2014 8:11 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 2:21 PM
Points: 391, Visits: 1,937
Perry Whittle (3/9/2014)
muthyala_51 (3/8/2014)
any suggestions?

For what?
anything now would just be speculation since the instance was restarted


I am trying to find the exact reason behind why the server behaved like this. Choked for memory even it had enough memory.
Post #1549053
Posted Sunday, March 9, 2014 8:44 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 3:06 PM
Points: 23,276, Visits: 31,996
Again, anything we say is just speculation. We don't have access to your server and the logs. You need to check the all the logs on the server to try and determine what occurred.



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1549054
Posted Sunday, March 9, 2014 2:57 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 11:19 AM
Points: 1,194, Visits: 2,215
muthyala_51 (3/9/2014)
Perry Whittle (3/9/2014)
muthyala_51 (3/8/2014)
any suggestions?

For what?
anything now would just be speculation since the instance was restarted


I am trying to find the exact reason behind why the server behaved like this. Choked for memory even it had enough memory.


To know the exact reason you should do a lot of troubleshooting not just shallow look ups. The information you provided was not enough. So pls try to answer the questions by the people so that you can get close to the solution.

--
SQLBuddy
Post #1549082
Posted Monday, March 10, 2014 1:35 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 2:21 PM
Points: 391, Visits: 1,937
I went through all the logs and grabbed some info for you guys. The following links gives us the exact scenario which happened at that time.....

Error 1: There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.

Error 2: New queries assigned to process on Node 0 have not been picked up by a worker thread in the last 1680 seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries.

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2917ea9b-d5d4-4a5f-839b-9f363041b685/sql-server-is-not-accepting-connections

http://www.sqlservercentral.com/blogs/aschenbrenner/2011/10/25/troubleshooting-threadpool-waits/

We have a 32 CPU on our production server and max worker threads setting is set to 2048. But according to microsoft recommendation it should be 960.
Post #1549457
Posted Monday, March 10, 2014 3:32 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 11:19 AM
Points: 1,194, Visits: 2,215
muthyala_51 (3/10/2014)
I went through all the logs and grabbed some info for you guys. The following links gives us the exact scenario which happened at that time.....

Error 1: There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.

Error 2: New queries assigned to process on Node 0 have not been picked up by a worker thread in the last 1680 seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries.

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2917ea9b-d5d4-4a5f-839b-9f363041b685/sql-server-is-not-accepting-connections

http://www.sqlservercentral.com/blogs/aschenbrenner/2011/10/25/troubleshooting-threadpool-waits/

We have a 32 CPU on our production server and max worker threads setting is set to 2048. But according to microsoft recommendation it should be 960.


Error 1: Check this

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL+Server&ProdVer=2000.80.760.0&EvtID=17803&EvtSrc=MSSQLServer

Error 2: Try changing max worker threads to default value and test it.

What are your CPU settings on the server ? MAXDOP, CPU Affinity etc .. Do you have CLR , Linked servers hosted on SQL Server ?


--
SQLBuddy
Post #1549508
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse