Production postmortemThe random high CPU

time to read 2 min | 253 words

A customer complained that every now and then RavenDB is hitting 100% CPU and stays there. They were kind enough to provide a minidump, and I started the investigation.

I loaded the minidump to WinDB and started debugging. The first thing you do with high CPU is rung the “!runaway” command, which sorts the threads by how busy they are:

image

I switched to the first thread (39) and asked for its stack, I highlighted the interesting parts:

image

This is enough to have a strong suspicion on what is going on. I checked some of the other high CPU threads and my suspicion was confirmed, but even from this single stack trace it is enough.

Pretty much whenever you see a thread doing high CPU within the Dictionary class it means that you are accessing it in a concurrent manner. This is unsafe, and may lead to strange effects. One of them being an infinite loop.

In this case, several threads were caught in this infinite loop. The stack trace also told us where in RavenDB we are doing this, and from there we could confirm that indeed, there is a rare set of circumstances that can cause a timer to fire fast enough that the previous timer didn’t have a chance to complete, and both of these timers will modify the same dictionary, causing the issue.

More posts in "Production postmortem" series:

  1. (06 Dec 2017) data corruption, a view from INSIDE the sausage
  2. (01 Dec 2017) The random high CPU
  3. (07 Aug 2017) 30% boost with a single line change
  4. (04 Aug 2017) The case of 99.99% percentile
  5. (02 Aug 2017) The lightly loaded trashing server
  6. (23 Aug 2016) The insidious cost of managed memory
  7. (05 Feb 2016) A null reference in our abstraction
  8. (27 Jan 2016) The Razor Suicide
  9. (13 Nov 2015) The case of the “it is slow on that machine (only)”
  10. (21 Oct 2015) The case of the slow index rebuild
  11. (22 Sep 2015) The case of the Unicode Poo
  12. (03 Sep 2015) The industry at large
  13. (01 Sep 2015) The case of the lying configuration file
  14. (31 Aug 2015) The case of the memory eater and high load
  15. (14 Aug 2015) The case of the man in the middle
  16. (05 Aug 2015) Reading the errors
  17. (29 Jul 2015) The evil licensing code
  18. (23 Jul 2015) The case of the native memory leak
  19. (16 Jul 2015) The case of the intransigent new database
  20. (13 Jul 2015) The case of the hung over server
  21. (09 Jul 2015) The case of the infected cluster