The tombstone needs to compact with every SSTable that contains data for the corresponding tombstone. For example the tombstone may be in that SSTable but some data the tombstone covers may possibly be in another SSTable. Only once all SSTables that contain relevant data have been compacted with the SSTable containing the tombstone can the tombstone be removed.
On 11 December 2017 at 01:08, tak...@fujitsu.com <tak...@fujitsu.com> wrote: > Hi All, > > > I'm using the SSTable with Size Tired Compaction Strategy with > 10 days gc grace period as default. > > And sstablemetadata command shows Estimated tombstone drop times > As follows after minor compaction on 9th Dec, 2018. > > (excerpt) > Estimated tombstone drop times:%n > 1510934467: 2475 * 2017.11.18 > 1510965112: 135 > 1510983500: 225 > 1511003962: 105 > 1511021113: 2280 > 1511037818: 30 > 1511055563: 120 > 1511075445: 165 > > > I just think there are records that should be deleted on > 18th Nov, 2018 in the SSTable by the output above. My understanding > is correct? > > If my understanding I correct, could someone tell me why those > expired data remains after compation? > > > > > Regards, > Takashima > > ---------------------------------------------------------------------- > Toshiaki Takashima > Toyama Fujitsu Limited > +810764553131, ext. 7260292355 > > ---------------------------------------------------------------------- > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > >
