There's a bit of headache around overlapping sstables being strictly safe to delete. https://issues.apache.org/jira/browse/CASSANDRA-13418 was added to allow the "I know it's not technically safe, but just delete it anyway" use case. For a lot of people who started using TWCS before 13418, "stop cassandra, remove stuff we know is expired, start cassandra" is a not-uncommon pattern in very high-write, high-disk-space use cases.
On Mon, Feb 11, 2019 at 12:34 PM Nitan Kainth <nitankai...@gmail.com> wrote: > Hi, > In regards to comment “Purging data is also straightforward, just > dropping SSTables (by a script) where create date is older than a > threshold, we don't even need to rely on TTL” > > Doesn’t the old sstables drop by itself? One ttl and gc grace seconds past > whole sstable will have only tombstones. > > > Regards, > > Nitan > > Cell: 510 449 9629 > > On Feb 11, 2019, at 2:23 PM, DuyHai Doan <doanduy...@gmail.com> wrote: > > Purging data is also straightforward, just dropping SSTables (by a script) > where create date is older than a threshold, we don't even need to rely on > TTL > >
