How many threads ? Any errors in the server logs ? What does noodtool tpstats and nodetool compactionstats say ?
Did you change compaction_strategy for the CF's ? By default cassandra will use as many compaction threads as you have cores, see concurrent_compactors in cassandra.yaml Have you set the JVM heap settings ? What does nodetool info show ? Hope that helps. ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 8/01/2012, at 3:51 PM, Caleb Rackliffe wrote: > Hi Everybody, > > JConsole tells me I've got CompactionReducer threads stacking up, consuming > memory, and never going away. Eventually, my Java process fails because it > can't allocate any more native threads. Here's my setup… > > Cassandra 1.0.5 on CentOS 6.0 > 4 GB of RAM > 50 GB SSD HD > Memtable flush threshold = 128 MB > compaction throughput limit = 16 MB/sec > Multithreaded compaction = true > > It may very well be that I'm doing something strange here, but it seems like > those compaction threads should go away eventually. I'm hoping the > combination of a low Memtable flush threshold, low compaction T/P limit, and > heavy write load doesn't mean those threads are hanging around because > they're actually not done doing their compaction tasks. > > Thanks, > > Caleb Rackliffe | Software Developer > M 949.981.0159 | ca...@steelhouse.com >
