Have you tried enabling 'unchecked_tombstone_compaction' on the affected tables?
On Tue, Mar 26, 2019 at 5:01 AM Nick Hatfield <nick.hatfi...@metricly.com> wrote: > How does one properly rid of sstables that have fallen victim to > overlapping timestamps? I realized that we had TWCS set in our CF which > also had a read_repair = 0.1 and after correcting this to 0.0 I can clearly > see the affects over time on the new sstables. However, I still have old > sstables that date back some time last year, and I need to remove them: > > Max: 09/05/2018 Min: 09/04/2018 Estimated droppable tombstones: > 0.8832057909932046 13G Mar 26 11:34 mc-254400-big-Data.db > > > What is the best way to do this? This is on a production system so any > help would be greatly appreciated. > > Thanks, > -- James Brown Engineer
