Cassandra version is : apache-cassandra-1.2.4
The latest 1.2 version is 1.2.13, you really should be on that.
commitlog_total_space_in_mb: 16
commitlog_segment_size_in_mb: 16
Reducing the total commit log size to 16 MB is a very bad idea, you should
return it to 4096 and the segment size to
Hi,
We are facing with a problem on Cassandra tuning. In that we have faced
with following OOM scenario[1], after running the system for 6 days. We
have tuned the cassandra with following values. These values also obtained
by going through huge number of testing cycles. But still it has gone
I'd suggest setting some cassandra jvm parameters so that you can analyze a
heap dump and peek through the gc logs. That'll give you some clues e.g.
if the memory problem is growing steadily or suddenly, and clues from a
peek at which object are using the memory.
-XX:+HeapDumpOnOutOfMemoryError
