RE: Massive deletes -> major compaction?

2017-09-22 Thread Steinmaurer, Thomas
nks still keep disk usage of already compacted SSTable alive. Regards, Thomas From: Durity, Sean R [mailto:sean_r_dur...@homedepot.com] Sent: Freitag, 22. September 2017 13:38 To: user@cassandra.apache.org Subject: RE: Massive deletes -> major compaction? Thanks for the pointer. I had never

RE: Massive deletes -> major compaction?

2017-09-22 Thread kurt greaves
e (like a newer one with the deletes…). It would only remove data if the tombstone is already in the same sstable. Sean Durity *From:* Jeff Jirsa [mailto:jji...@gmail.com] *Sent:* Thursday, September 21, 2017 2:51 PM *To:* user@cassandra.apache.org *Subject:* Re: Massive deletes -> major

RE: Massive deletes -> major compaction?

2017-09-22 Thread Durity, Sean R
...@gmail.com] On Behalf Of Jon Haddad Sent: Thursday, September 21, 2017 2:59 PM To: user Subject: Re: Massive deletes -> major compaction? Have you considered the fantastic DeletingCompactionStrategy? https://github.com/protectwise/cassandra-util/tree/master/deleting-compaction-strategy<

RE: Massive deletes -> major compaction?

2017-09-21 Thread Durity, Sean R
tombstone is already in the same sstable. Sean Durity From: Jeff Jirsa [mailto:jji...@gmail.com] Sent: Thursday, September 21, 2017 2:51 PM To: user@cassandra.apache.org Subject: Re: Massive deletes -> major compaction? The major compaction is most efficient but can temporarily double (nea

Re: Massive deletes -> major compaction?

2017-09-21 Thread Jon Haddad
Have you considered the fantastic DeletingCompactionStrategy? https://github.com/protectwise/cassandra-util/tree/master/deleting-compaction-strategy > On Sep 21, 2017, at 11:51 AM, Jeff Jirsa wrote: > >

Re: Massive deletes -> major compaction?

2017-09-21 Thread Jeff Jirsa
The major compaction is most efficient but can temporarily double (nearly) disk usage - if you can afford that, go for it. Alternatively you can do a user-defined compaction on each sstable in reverse generational order (oldest first) and as long as the data is minimally overlapping it’ll purge

Massive deletes -> major compaction?

2017-09-21 Thread Durity, Sean R
Cassandra version 2.0.17 (yes, it's old - waiting for new hardware/new OS to upgrade) In a long-running system with billions of rows, TTL was not set. So a one-time purge is being planned to reduce disk usage. Records older than a certain date will be deleted. The table uses size-tiered compact