On Tue, Mar 31, 2015 at 9:12 AM, Jens Rantil <jens.ran...@tink.se> wrote:
> One issue when you are running a JVM and start running out of memory is > that the JVM can start throwing `OutOfMemoryError` in any thread - not > necessarily in the thread which is taking all the memory. I've seen this > happen multiple times. If this happened to you, a critical Cassandra thread > could have died and brought the whole Cassandra DB with itself. > Jens is correct that the JVM has few options as to what to do when it runs out of heap : https://issues.apache.org/jira/browse/CASSANDRA-7507 Expands a bit on Cassandra specific behavior here. But basically, once you've OOMed (any generation of) the heap, you almost certainly want to stop or re-start the JVM, even if it hasn't crashed itself. =Rob
