Hi, Is your OOM on heap or on native memory ? Since 2.1 put a lot of things on native memory I would say that it is almost always bad to have 6 GB out of 8 for the heap (unless you have a very small data set), since in the 2 GB remaining you have to keep bloom filters, indexes and more + Page caching if you have free space in there...
If the OOM is in the heap, is there any sign of pressure in the logs (PARNEW / CMS) ? Also did you activated GC logs to troubleshoot this manually or through a third party application ? +1 with Sebastien for the hprof analyse. Rob might also be right by pointing the memory link. Hope this will help. C*heers, Alain 2015-06-15 19:39 GMT+02:00 Robert Coli <rc...@eventbrite.com>: > On Sat, Jun 13, 2015 at 4:39 AM, Oleksandr Petrov < > oleksandr.pet...@gmail.com> wrote: > >> We're using Cassandra, recently migrated to 2.1.6, and we're experiencing >> constant OOMs in one of our clusters. >> > > Maybe this memory leak? > > https://issues.apache.org/jira/browse/CASSANDRA-9549 > > =Rob >
