Sounds a lot like it's running out of memory. Check your logs for GCInspector lines.
Easiest solution: increase the argument to Xmx in cassandra.in.sh. On Mon, Aug 2, 2010 at 8:05 AM, Jean-Yves LEBLEU <jleb...@gmail.com> wrote: > Hi all, > > We have a cassandra installation with two nodes in a ring, replication > factor = 2, some times cassandra becomes non-responsive, it takes > about three minutes before answering to a get. > Do you have any idea of what we should check when it happens ? Or what > could cause the problem. > We are using cassandra release 6.3. > Thanks & regards. > Jean-Yves > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of Riptano, the source for professional Cassandra support http://riptano.com
