There were no errors in the log (other than the messages dropped exception
pasted below), and the node does recover. We have only a small number of
secondary indexes (3 in the whole system).
However, I went through the cassandra code, and I believe I've worked through
this problem.
Just to
To put in other words, Cassandra will lock down all tables until all pending
flush requests fit in the pending queue.
This was the first issue I looked at in my Cassandra SF talk
http://www.datastax.com/events/cassandrasummit2012/presentations
I've seen it occur more often with
Love the Mars lander analogies :)
On Sep 23, 2012, at 5:39 PM, aaron morton wrote:
To put in other words, Cassandra will lock down all tables until all pending
flush requests fit in the pending queue.
This was the first issue I looked at in my Cassandra SF talk
Any errors in the log ?
The node recovers ?
Do you use secondary indexes ? If so check comments for
memtable_flush_queue_size in the yaml. if this value is too low writes may back
up. But I would not expect it to cause dropped messages.
nodetool info also shows we have over a gig of
Hello,
While under load, we have occasionally been seeing messages dropped errors in
our cassandra log. Doing some research, I understand this is part of
Cassandra's design to shed load, and we should look at the tpstats-like output
to determine what should be done to resolve the situation.
INFO [ScheduledTasks:1] 2012-09-17 06:28:03,839 StatusLogger.java (line 72)
MemtablePostFlusher 1 5 0
INFO [ScheduledTasks:1] 2012-09-17 06:28:03,840 StatusLogger.java (line 72)
FlushWriter 1 5 0
Looks suspiciously like
