Re: Moving all LCS SSTables to a repaired state

See my other email to this list that you replied to (I most recently replied late last week), titled "Cassandra isn't compacting old files". It's not just a few. It's tens/hundreds. I'm worried there's some "starvation" going on and disk is being filled with data that could be compacted away. 

Re: Moving all LCS SSTables to a repaired state

Is there any specific reason you are trying to achieve this? It shouldn't really matter if you have a few SSTables in the unrepaired pool.​

Re: Moving all LCS SSTables to a repaired state

We are on 2.2.11 so we're all right on that front. The advice is difficult to implement unfortunately, with so many nodes. Thanks for the information!On Sunday, August 20, 2017, 4:28:36 PM PDT, kurt greaves wrote: Correction: Full repairs do mark SSTables as repaired in 2.2 (CASSANDRA-7586). M

Re: Moving all LCS SSTables to a repaired state

Correction: Full repairs do mark SSTables as repaired in 2.2 (CASSANDRA-7586 ). My mistake, I thought that was only introduced in 3.0. Note that if mixing full and incremental repairs you probably want to be using at least 2.2.10 because of CASS

Re: Moving all LCS SSTables to a repaired state

Pretty much, I wouldn't set your heart on having 0 unrepaired SSTables.

Re: Moving all LCS SSTables to a repaired state

That's the only way to get this done then, break writes and fix them with incremental repairs? On Friday, August 18, 2017, 5:17:38 PM PDT, kurt greaves wrote: You need to run an incremental repair for sstables to be marked repaired. However only if all of the data in that Sstable is repaired

Re: Moving all LCS SSTables to a repaired state

You need to run an incremental repair for sstables to be marked repaired. However only if all of the data in that Sstable is repaired during the repair will you end up with it being marked repaired, otherwise an anticompaction will occur and split the unrepaired data into its own sstable. It's pret

Moving all LCS SSTables to a repaired state

I have a table that uses LeveledCompactionStrategy on Cassandra 2.2. At the moment, it has two SSTables, both in level 1, one that's repaired and one that isn't. $ sstablemetadata lb-135366-big-Data.db | head SSTable: /home/cassandra/data/my_keyspace/my_table/lb-135366-big Partitioner: org.apache