Production postmortemThe industry at large

time to read 1 min | 100 words

The following is a really good study on real world production crashes:

Simple Testing Can Prevent Most Critical Failures:
An Analysis of Production Failures in Distributed
Data-Intensive Systems

It makes for fascinating reading, especially since the include the details of the root cause of some of the errors. I wasn’t sure whatever to cringe or sympathize Open-mouthed smile.

image

More posts in "Production postmortem" series:

  1. (29 Apr 2022) Deduplicating replication speed
  2. (25 Apr 2022) The network latency and the I/O spikes
  3. (22 Apr 2022) The encrypted database that was too big to replicate
  4. (20 Apr 2022) Misleading security and other production snafus
  5. (03 Jan 2022) An error on the first act will lead to data corruption on the second act…
  6. (13 Dec 2021) The memory leak that only happened on Linux
  7. (17 Sep 2021) The Guinness record for page faults & high CPU
  8. (07 Jan 2021) The file system limitation
  9. (23 Mar 2020) high CPU when there is little work to be done
  10. (21 Feb 2020) The self signed certificate that couldn’t
  11. (31 Jan 2020) The slow slowdown of large systems
  12. (07 Jun 2019) Printer out of paper and the RavenDB hang
  13. (18 Feb 2019) This data corruption bug requires 3 simultaneous race conditions
  14. (25 Dec 2018) Handled errors and the curse of recursive error handling
  15. (23 Nov 2018) The ARM is killing me
  16. (22 Feb 2018) The unavailable Linux server
  17. (06 Dec 2017) data corruption, a view from INSIDE the sausage
  18. (01 Dec 2017) The random high CPU
  19. (07 Aug 2017) 30% boost with a single line change
  20. (04 Aug 2017) The case of 99.99% percentile
  21. (02 Aug 2017) The lightly loaded trashing server
  22. (23 Aug 2016) The insidious cost of managed memory
  23. (05 Feb 2016) A null reference in our abstraction
  24. (27 Jan 2016) The Razor Suicide
  25. (13 Nov 2015) The case of the “it is slow on that machine (only)”
  26. (21 Oct 2015) The case of the slow index rebuild
  27. (22 Sep 2015) The case of the Unicode Poo
  28. (03 Sep 2015) The industry at large
  29. (01 Sep 2015) The case of the lying configuration file
  30. (31 Aug 2015) The case of the memory eater and high load
  31. (14 Aug 2015) The case of the man in the middle
  32. (05 Aug 2015) Reading the errors
  33. (29 Jul 2015) The evil licensing code
  34. (23 Jul 2015) The case of the native memory leak
  35. (16 Jul 2015) The case of the intransigent new database
  36. (13 Jul 2015) The case of the hung over server
  37. (09 Jul 2015) The case of the infected cluster