On Wed, Aug 6, 2014 at 1:12 PM, Robert Coli <rc...@eventbrite.com> wrote:
> On Wed, Aug 6, 2014 at 1:11 AM, Duncan Sands <duncan.sa...@gmail.com> > wrote: > >> this doesn't look like an OOM to me. If the kernel OOM kills Cassandra >> then Cassandra instantly vaporizes, and there will be nothing in the >> Cassandra logs (you will find information about the OOM in the system logs >> though, eg in dmesg). In the log snippet above you see an orderly >> shutdown, this is completely different to the instant OOM kill. >> > > Not really. > > https://issues.apache.org/jira/browse/CASSANDRA-7507 > To be clear, there's two different OOMs here, I am talking about the JVM OOM, not system level. As CASSANDRA-7507 indicates, JVM OOM does not necessarily result in the cassandra process dying, and can in fact trigger clean shutdown. System level OOM will in fact send the equivalent of KILL, which will not trigger the clean shutdown hook in Cassandra. =Rob
