> CASSANDRA_HEAPDUMP_DIR
Is for JVM out of memory. You were seeing the OS kill the JVM because of low os
memory.
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 22/08/2012, at 4:28 PM, Xu Renjie wrote:
> Guille,
>Thanks for your re
Guille,
Thanks for your reply. I seem to find where is the problem. I guess it
is because memory is used up not the jvm heap( I use micro ec2 instance
just for toy use). Seems that I have set the cassandra heap too high to
avoid gc to effect my performance, but the total memory is not enough. So
Xu, what's your configuration?
How many CF, how much data (size/rows/cols), how many clients
operations/sec and how much memory assigned for the heap?
Guille
On Wed, Aug 22, 2012 at 12:09 AM, Xu Renjie wrote:
> Hi, all
>I have a problem about the log. I have set the CASSANDRA_HEAPDUMP_DIR
BTW, I have checked the jvm by jps that the options are correctly added.
On Wed, Aug 22, 2012 at 11:09 AM, Xu Renjie wrote:
> Hi, all
>I have a problem about the log. I have set the CASSANDRA_HEAPDUMP_DIR
> in the cassandra-env.in file to some path to store the dump file
> when OutOfMemory e
Hi, all
I have a problem about the log. I have set the CASSANDRA_HEAPDUMP_DIR in
the cassandra-env.in file to some path to store the dump file
when OutOfMemory exception happens. But after out of memory happens(I judge
it from the /var/log/messages which says "kernel: out of memory:
kill process
