And It All Went Horribly Wrong: Debugging Production ... - Joyent

More documents

Recommendations

Info

Disaster Porn III Thursday, November 17, 2011
Postmortem challenges • Must have the mechanism for saving state on failure • Must record sufficient state — which must include program text as well as program data • Must have sufficient state present in DRAM to allow for debugging (correctly formed stacks are a must, as is the symbol table; type information is invaluable) • Must manage state such that storage is not overrun by a repeatedly pathological system • These challenges are real but surmountable — and several open source systems have met them... Thursday, November 17, 2011
Page 1 and 2: And It All Went Horribly Wrong: Deb
Page 3 and 4: In the beginning... Sir Maurice Wil
Page 5 and 6: Debugging through the ages • As s
Page 7 and 8: Do we still need to care about fail
Page 9 and 10: Wait, it gets worse • This assume
Page 11 and 12: Debugging in the modern era • Fai
Page 13: Postmortem advantages • There is
Page 17 and 18: Postmortem debugging • Postmortem
Page 19 and 20: Postmortem debugging: node.js • D
Page 21 and 22: Debugging transient component failu
Page 23 and 24: DTrace • Facility for dynamic ins
Page 25 and 26: DTrace for node.js • Given the na
Page 27 and 28: Extending DTrace into the VMs • T
Page 29: Thank you! • Dave Pacheco (@dapsa

And It All Went Horribly Wrong: Debugging Production ... - Joyent

Create successful ePaper yourself

Delete template?

Save as template?