There is no way to reverse a compaction. You can initiate a user compaction on a single file though, see nodetool (i think) or the JMX interface. Cheers
----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 1/02/2012, at 4:10 AM, Micah Hausler wrote: > A related question, is there any way to reverse a major compaction without > loosing performance? Do I just have to wait it out? > > Micah Hausler > > On Jan 30, 2012, at 7:50 PM, Roshan Pradeep wrote: > >> Thanks Aaron for the perfect explanation. Decided to go with automatic >> compaction. Thanks again. >> >> On Wed, Jan 25, 2012 at 11:19 AM, aaron morton <aa...@thelastpickle.com> >> wrote: >> The issue with major / manual compaction is that it creates a one file. One >> big old file. >> >> That one file will not be compacted unless there are >> (min_compaction_threshold -1) other files of a similar size. So thombstones >> and overwrites in that file may not be purged for a long time. >> >> If you go down the manual compaction path you need to keep doing it. >> >> If you feel you need to do it do it, otherwise let automatic compaction do >> it's thing. >> Cheers >> >> >> ----------------- >> Aaron Morton >> Freelance Developer >> @aaronmorton >> http://www.thelastpickle.com >> >> On 25/01/2012, at 12:47 PM, Roshan wrote: >> >>> Thanks for the reply. Is the major compaction not recommended for Cassandra >>> 1.0.6? >>> >>> -- >>> View this message in context: >>> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Different-size-of-SSTable-are-remain-in-the-system-without-compact-tp7218239p7222322.html >>> Sent from the cassandra-u...@incubator.apache.org mailing list archive at >>> Nabble.com. >> >> >
