"user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: RE: cassandra just gone..no heap dump, no log info
We faced same issue sometimes too.
1) Linux OOM killer kill your Cassandra process. You should find this event log
in /var/log/message.
2
; Date: Wed, 18 Sep 2013 06:59:07 -0600
> Subject: Re: cassandra just gone..no heap dump, no log info
>
> Swappiness is set to 60 though cassandra recommendations are to turn swap
> completely off(we still have not done that as far as I know though) and sure
> enough linux killed it
We ran into this while tuning heap sizes. With Cassandra 1.2 making use of
off-heap memory, if we made our JVM too large relative to the server
memory, the system would just bail. We found for our app that the limit of
the JVM size relative to server memory was about 50%.
On Wed, Sep 18, 2013 a
lt;mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Wednesday, September 18, 2013 6:57 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: cassandra just gone..no heap dump, no log i
tember 18, 2013 6:45 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: cassandra just gone..no heap dump, no log info
A random guess - possibly an OOM (Out of Memory) where Linux will kill a
process to recover memory when
This shouldn't happen if you have swap active in the server
On Wednesday, September 18, 2013, Franc Carter wrote:
>
> A random guess - possibly an OOM (Out of Memory) where Linux will kill a
> process to recover memory when it is desperately low on memory. Have a look
> in either your syslog outp
Check if java process got crashed. You can find hs_err*.log file in root
directory or cassandra working directory or temporary files directory.
Information in this log file can give an idea about failure.
On Wed, Sep 18, 2013 at 5:51 PM, Hiller, Dean wrote:
> Anyone know how to debug cassandra
A random guess - possibly an OOM (Out of Memory) where Linux will kill a
process to recover memory when it is desperately low on memory. Have a look
in either your syslog output of the output of dmesg
cheers
On Wed, Sep 18, 2013 at 10:21 PM, Hiller, Dean wrote:
> Anyone know how to debug cassa
