You can use the JMX forceUserDefinedCompaction operation to compact each SSTable individually.
https://github.com/hancockks/cassandra-compact-cf On Sat, Nov 1, 2014 at 11:18 AM, Jens Rantil <jens.ran...@tink.se> wrote: > Hi, > > I recently ran a migration where I modified (essentially, deleted and > inserted) a large number of clustering keys. This obviously created a lot > of tombstones and now I am receiving warnings in my logs that number of > tombstones are above a certain threshold when I query all rows for a > certain partition key. I suspect this might lead to RPC Timeouts in certain > cases. > > The migration was done more than `gc_grace_seconds` ago, so I can safely > remove these tombstones by now. > > Question: Is there any way for me to force Cassandra to purge tombstones > for all sstables of a certain columnfamily (running LCS)? I asked this > quesion on IRC and AFAIK the only way would be to switch to SizeTiered > compaction strategy, issuing a major compaction, and then switching back to > LCS. Would there be any implications/side effects executing this procedure? > > Thanks, > Jens > > ——— Jens Rantil Backend engineer Tink AB Email: jens.ran...@tink.se > Phone: +46 708 84 18 32 Web: www.tink.se Facebook Linkedin Twitter >
