Having 2056 live SSTables is very odd. Minor compaction should automatically reduce that number. What settings for min_compaction_threshold and max_compaction_threshold did you use when creating the CF ?
You can check them with node tool getcompactionthreshold . The default is min 4 and max 32. You can also set them using nodetool setcompactionthreshold (Note the value is not persisted across a restart). To provoke a minor compaction run nodetool flush. Minor compactions are preferred to major as they keep SSTables with the compaction buckets, where as major creates a single large file which will not be compacted again for a long time. Hope that helps. ----------------- Aaron Morton Freelance Cassandra Developer @aaronmorton http://www.thelastpickle.com On 1 Aug 2011, at 17:08, Teijo Holzer wrote: > Looks like a broken node, just restart Cassandra on that node. Might want to > wait for the compaction to finish on the other nodes. > > Also, don't forget to JMX gc() manually after the compaction has finished to > delete the files on each node. > > On 01/08/11 16:29, myreasoner wrote: >> On the node that the compaction returned almost immediately: >> >> *woot@n50:~$ /opt/cassandra/bin/nodetool -h localhost compactionstats >> pending tasks: 66* >> >> However, messages shown on other nodes are: >> compaction type: Major >> keyspace: MyKeyspace >> column family: Fingerprint >> bytes compacted: 25505066421 >> bytes total: 45573108438 >> compaction progress: 55.97% >> ----------------- >> pending tasks: 1 >> >> >> >> -- >> View this message in context: >> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Read-latency-is-over-1-minute-on-a-column-family-with-400-000-rows-tp6639649p6639836.html >> Sent from the cassandra-u...@incubator.apache.org mailing list archive at >> Nabble.com. >
