There have been a lot of discussions about GC tuning on the mail thread. Here's
a really quick set of guidelines I use, please search the mail archive if it
does not answer your question.
If heavy GC activity correlates with cassandra compaction, do one or more of:
* reduce
Hello,
Just to wrap up on my part of this thread, tuning CMS compaction threshold
(-XX:CMSInitiatingOccupancyFraction) to 70 appears to resolved my issues with
the memory warnings. However, I don't believe this would be a solution to all
the issues mentioned below. Although, it does make
We are using DSE, which I believe is also 1.1.9. We have basically had a
non-usable cluster for months due to this error. In our case, once it starts
doing this it starts flushing sstables to disk and eventually fills up the disk
to the point where it can't compact. If we catch it soon
[mailto:mthero...@yahoo.com]
Sent: Friday, April 19, 2013 6:00 PM
To: user@cassandra.apache.org
Subject: Advice on memory warning
Hello,
We've recently upgraded from m1.large to m1.xlarge instances on AWS to handle
additional load, but to also relieve memory pressure. It appears to have
accomplished
Hello,
We've recently upgraded from m1.large to m1.xlarge instances on AWS to handle
additional load, but to also relieve memory pressure. It appears to have
accomplished both, however, we are still getting a warning, 0-3 times a day, on
our database nodes:
WARN [ScheduledTasks:1] 2013-04-19
