Thanks for sharing! I love reading articles like this that cover multiple layers of a system as part of an investigation.
Can you clarify the comment about -XX:-HeapDumpOnOutOfMemoryError? I believe this would not restart the JVM and instead would log the contents of the heap (which is still very valuable for post-mortem analysis). Would you also recommend something like -XX:OnOutOfMemoryError="kill %p", under the assumption that a process monitor like upstart or monit will bring it back up? --Chris Nauroth On 5/8/15, 9:46 AM, "Patrick Hunt" <[email protected]> wrote: >There's a great post on Pager Duty today, >http://www.pagerduty.com/blog/the-discovery-of-apache-zookeepers-poison-pa >cket/ >some good comments on hackernews too >https://news.ycombinator.com/item?id=9509698 > >If I understand correctly bug1 is already fixed: >https://issues.apache.org/jira/browse/ZOOKEEPER-2146 >should be released in 3.4.7+ > >However bug2 >https://issues.apache.org/jira/browse/ZOOKEEPER-602 >is just in 3.5 and not 3.4.x. Note my push back in the comments on 602 re >risk vs reward. Evan makes a good case for including it. :-) > >We should also recommend that folks run with >-XX:-HeapDumpOnOutOfMemoryError >I would think. That should have caused the jvm to restart when bug1 was >hit. > >Thoughts? Hongchao can you confirm that 2146 fixes bug 1? > >Patrick
