I issued another major compaction just now and a brand new SSTable in Level 2 has an Estimated droppable tombstone value of 0.64. I don't know how accurate that is.
On Tuesday, August 22, 2017, 9:33:34 PM PDT, Sotirios Delimanolis <sotodel...@yahoo.com.INVALID> wrote: What do you mean by "a single SSTable"? SSTable size is set to 200MB and there are ~ 100 SSTables in that previous example in Level 3. This previous example table doesn't have a TTL, but we do delete rows. I've since compacted the table so I can't provide the previous "Estimated droppable tombstones", but it was > 0.3. I've set the threshold to 0.25, but unchecked_tombstone_compaction is false. Perhaps setting it to true would eventually compact individual SSTables. I agree that I am probably not creating enough data at the moment, but what got me into this situation in the first place? All (+/- a couple) SSTables in each level are last modified on the same date. On Tuesday, August 22, 2017, 5:16:27 PM PDT, kurt greaves <k...@instaclustr.com> wrote: LCS major compaction on 2.2 should compact each level to have a single SSTable. It seems more likely to me that you are simply not generating enough data to require compactions in L3 and most data is TTL'ing before it gets there. Out of curiosity, what does sstablemetadata report for Estimated droppable tombstones on one of those tables, and what is your TTL?
