Awesome, thanks again!
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Wednesday, March 27, 2019 1:36 PM
To: cassandra
Subject: Re: TWCS Compactions & Tombstones
You would need to swap your class from the com.jeffjirsa variant (probably from
2.1 / 2.2) to the official TWCS class.
een this yet. So we have this
> enabled, I guess it will just take time to finally chew through it all?
>
>
>
> *From:* Jeff Jirsa [mailto:jji...@gmail.com]
> *Sent:* Tuesday, March 26, 2019 9:41 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: TWCS Compactions &
Awesome, thank you Jeff. Sorry I had not seen this yet. So we have this
enabled, I guess it will just take time to finally chew through it all?
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Tuesday, March 26, 2019 9:41 PM
To: user@cassandra.apache.org
Subject: Re: TWCS Compactions
Have you tried enabling 'unchecked_tombstone_compaction' on the affected
tables?
On Tue, Mar 26, 2019 at 5:01 AM Nick Hatfield
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
the sstable data so that I can verify that it is
old data, other than by the min / max timestamps?
Thanks for your help
From: Rahul Singh [mailto:rahul.xavier.si...@gmail.com]
Sent: Tuesday, March 26, 2019 9:24 PM
To: user
Subject: Re: TWCS Compactions & Tombstones
What's your timewindow? Roughly
Or Upgrade to a version with
https://issues.apache.org/jira/browse/CASSANDRA-13418 and enable that feature
--
Jeff Jirsa
> On Mar 26, 2019, at 6:23 PM, Rahul Singh wrote:
>
> What's your timewindow? Roughly how much data is in each window?
>
> If you examine the sstable data and see that
What's your timewindow? Roughly how much data is in each window?
If you examine the sstable data and see that is truly old data with little
chance that it has any new data, you can just remove the SStables. You can
do a rolling restart -- take down a node, remove mc-254400-* and then start
it up.
