cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Віталій Тимчишин <>
Subject Cassandra OOM
Date Tue, 03 Jan 2012 10:18:56 GMT

We are using cassandra for some time in our project. Currently we are on
1.1 trunk (it was accidental migration, but since it's hard to migrate back
and it's performing nice enough we are currently on 1.1).
During New Year holidays one of the servers've produces a number of OOM
messages in the log.
According to heap dump taken, most of the memory is taken by MutationStage
queue (over 2millions of items).
So, I am curious now if cassandra have any flow control for messages? We
are using Quorum for writes and it seems to me that one slow server may
start getting more messages than it can consume. The writes will still
succeed performed by other servers in the replication set.
If there is no flow control, it should eventually get OOM. Is it the case?
Are there any plans to handle this?
BTW: A lot of memory (~half) is taken by Inet4Address objects, so making a
cache of such objects would make this problem less possible.

Best regards,
 Vitalii Tymchyshyn

View raw message