What else are you seeing that correlates with "unresponsive?" lots of pending tasks in stage queues?
high cpu in a single thread? swapping? (I sent a github pull request, but I've updated http://github.com/jbellis/cassandra-munin-plugins with a lot more metrics to monitor.) On Thu, May 27, 2010 at 12:32 AM, James Golick <jamesgol...@gmail.com> wrote: > We're seeing RAM usage continually climb until eventually, cassandra becomes > unresponsive. > The JVM isn't OOM'ing. It has only committed 14/24GB of memory. So, I am > assuming that the memory usage is related to mmap'd IO. Fair assumption? > I tried setting the IO mode to standard, but it seemed to be a little slower > and couldn't get the machine to come back online with adequate read > performance, so I set it back. I'll have to write a solid cache warming > script if I'm going to try that again. > Any other ideas for what might be causing the issue? Is there something I > should monitor or look at next time it happens? > Thanks -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
