There are a few factors: sometimes data that is in a fat partition clogs up
the heap space / memtable space and tombstones don't help that much either.
This is worsened by data skew . I agree , if CMS is working for now,
continue using it and then upgrade to better versions of Java / C*.
Few thing
I would strongly suggest you consider an upgrade to 3.11.x. I found it
decreased space needed by about 30% in addition to significantly lowering
GC.
As a first step, though, why not just revert to CMS for now if that was
working ok for you? Then you can convert one host for diagnosis/tuning so
t
Hello Team,
I have a cluster of 17 nodes in production.(8 and 9 nodes in 2 DC).
Cassandra version: 2.0.11
Client connecting using thrift over port 9160
Jdk version : 1.8.066
GC used : G1GC (16GB heap)
Other GC settings:
Maxgcpausemillis=200
Parallels gc threads=32
Concurrent gc threads= 10
Initiat
