Debugging the Deadlock for the Scheduler

5,827 views

Published on

Slide deck used for my SQL Saturday 76 presentatio on "Debugging the deadlock for the scheduler"

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
5,827
On SlideShare
0
From Embeds
0
Number of Embeds
4,806
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Debugging the Deadlock for the Scheduler

  1. 1. www.TroubleshootingSQL.comwww.troubleshootingsql.com http://twitter.com/banerjeeamit http://twitter.com/TblShootingSQL www.facebook.com/TroubleshootingSQL
  2. 2. • What is a Deadlocked Scheduler?• What are my options?• Common Reasons• Proactive action• Reactive action
  3. 3. Scheduler • A scheduler is a logical CPU that is used by SQL Server workersWorker thread • Only a single worker can own the scheduler Reason • Out of worker threads to process incoming requests • When a deadlocked scheduler issue is detected 17888 and over 50 percent of the workers are waiting on a common resource type
  4. 4. DAC Notifications Post-mortem• Collect DMV • Windows Event • Analyze the outputs Log alerts logs • Alerts on new • Debug the memory dump memory dump files
  5. 5. All schedulers have encountered a 17883 condition All workers are blocked on a critical resource. Eg. SpinlocksAll workers are executing a long-running query: Parallelism and Lock Blocking Open Transactions
  6. 6. www.troubleshootingsql.com http://twitter.com/banerjeeamit http://twitter.com/TblShootingSQL www.facebook.com/TroubleshootingSQLhttp://www.sqlserverlaunch.com/ww/Home
  7. 7. http://msdn.microsoft.com/en-us/library/cc917684.aspxhttp://troubleshootingsql.com/tag/deadlocked-schedulers/http://msdn.microsoft.com/en-us/windows/hardware/gg463009http://msdl.microsoft.com/download/symbolshttp://support.microsoft.com/kb/319892/en-us

×