How It Works: 17888 - All Schedulers on Node Appear Deadlocked

Published Jan 15 2019 11:04 AM 710 Views
Microsoft
First published on MSDN on Sep 03, 2008

Error 17888: All schedulers on Node ## appear deadlocked due to a large number of worker threads waiting on <<RESOURCE>>. Process Utilization ##%.

SQL Server creates a Scheduler Monitor thread for each node.   One of the Scheduler Monitor tasks is to watch the schedulers assigned to the node for progress.   Slow progress triggers additional checks; among them is the 17888 check.

The 17888 condition is when Scheduler Monitor detects the workers are not progressing and if this is because of a common resource bottleneck.

The following is an example showing clients not processing results.  This could be a bad application, router problems, or other network issue.

Example: All schedulers on Node 0 appear deadlocked due to a large number of worker threads waiting on ASYNC_NETWORK_IO. Process Utilization 0%.

The message indicates that a large number of workers are waiting on network I/O and until the I/O completes the SQL Server will remain bottlenecked.

Address the <<RESOURCE>> bottleneck to resolve the problem.   The DAC connection is a great way to obtain additional information about the bottleneck.

Reference: How To Diagnose and Correct Errors 17883, 17884, 17887, and 17888
http://www.microsoft.com/technet/prodtechnol/sql/2005/diagandcorrecterrs.mspx

Bob Dorr
SQL Server Principal Escalation Engineer
%3CLINGO-SUB%20id%3D%22lingo-sub-315545%22%20slang%3D%22en-US%22%3EHow%20It%20Works%3A%2017888%20-%20All%20Schedulers%20on%20Node%20Appear%20Deadlocked%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-315545%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Sep%2003%2C%202008%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3E%3CB%3EError%20%3C%2FB%3E%20%3CB%3E%2017888%3A%20%3C%2FB%3E%20All%20schedulers%20on%20Node%20%23%23%20appear%20deadlocked%20due%20to%20a%20large%20number%20of%20worker%20threads%20waiting%20on%20%26lt%3B%3CRESOURCE%3E%26gt%3B.%20Process%20Utilization%20%23%23%25.%3C%2FRESOURCE%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3ESQL%20Server%20creates%20a%20Scheduler%20Monitor%20thread%20for%20each%20node.%26nbsp%3B%26nbsp%3B%20One%20of%20the%20Scheduler%20Monitor%20tasks%20is%20to%20watch%20the%20schedulers%20assigned%20to%20the%20node%20for%20progress.%26nbsp%3B%26nbsp%3B%20Slow%20progress%20triggers%20additional%20checks%3B%20among%20them%20is%20the%2017888%20check.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EThe%2017888%20condition%20is%20when%20Scheduler%20Monitor%20detects%20the%20workers%20are%20not%20progressing%20and%20if%20this%20is%20because%20of%20a%20common%20resource%20bottleneck.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EThe%20following%20is%20an%20example%20showing%20clients%20not%20processing%20results.%26nbsp%3B%20This%20could%20be%20a%20bad%20application%2C%20router%20problems%2C%20or%20other%20network%20issue.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CBLOCKQUOTE%3E%0A%20%20%20%3CP%3E%3CB%3EExample%3A%20%3C%2FB%3E%20All%20schedulers%20on%20Node%200%20appear%20deadlocked%20due%20to%20a%20large%20number%20of%20worker%20threads%20waiting%20on%20ASYNC_NETWORK_IO.%20Process%20Utilization%200%25.%3C%2FP%3E%0A%20%20%20%3CP%3E%3C%2FP%3E%0A%20%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3C%2FBLOCKQUOTE%3E%0A%20%20%3CP%3EThe%20message%20indicates%20that%20a%20large%20number%20of%20workers%20are%20waiting%20on%20network%20I%2FO%20and%20until%20the%20I%2FO%20completes%20the%20SQL%20Server%20will%20remain%20bottlenecked.%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EAddress%20the%20%26lt%3B%3CRESOURCE%3E%26gt%3B%20bottleneck%20to%20resolve%20the%20problem.%26nbsp%3B%26nbsp%3B%20The%20DAC%20connection%20is%20a%20great%20way%20to%20obtain%20additional%20information%20about%20the%20bottleneck.%3C%2FRESOURCE%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3CB%3E%20Reference%3A%20%3C%2FB%3E%20How%20To%20Diagnose%20and%20Correct%20Errors%2017883%2C%2017884%2C%2017887%2C%20and%2017888%20%3CBR%20%2F%3E%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Ftechnet%2Fprodtechnol%2Fsql%2F2005%2Fdiagandcorrecterrs.mspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20http%3A%2F%2Fwww.microsoft.com%2Ftechnet%2Fprodtechnol%2Fsql%2F2005%2Fdiagandcorrecterrs.mspx%20%3C%2FA%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3EBob%20Dorr%20%3CBR%20%2F%3E%20SQL%20Server%20Principal%20Escalation%20Engineer%20%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-315545%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Sep%2003%2C%202008%20Error%2017888%3A%20All%20schedulers%20on%20Node%20%23%23%20appear%20deadlocked%20due%20to%20a%20large%20number%20of%20worker%20threads%20waiting%20on%20%26lt%3B%3CRESOURCE%3E%26gt%3B.%3C%2FRESOURCE%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-315545%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESQL%20OS%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Jan 15 2019 11:04 AM
Updated by: