Re: state of incremental repairs in cassandra 3.x

[Alexander DEJANOVSKI]

Hi James,

I'd recommend to upgrade to 4.0.1 if you intend to use incremental repair.
The changes from CASSANDRA-9143
 are massive and
couldn't be backported to the 3.11 branch.

When moving to incremental, and in order to limit anticompaction on the
first run, I'd recommend to:
- mark all sstables as repaired
- run a full repair
- schedule very regular (daily) incremental repairs

Bye,

Alex


Le jeu. 16 sept. 2021 à 23:03, C. Scott Andreas  a
écrit :

> Hi James, thanks for reaching out.
>
> A large number of fixes have landed for Incremental Repair in the 3.x
> series, though it's possible some may have been committed to 4.0 without a
> backport. Incremental repair works well on Cassandra 4.0.1. I'd start here
> to ensure you're picking up all fixes that went in, though I do think it's
> likely to work well on a recent 3.0.x build as well (I'm less familiar with
> the 3.11.x series).
>
> – Scott
>
> On Sep 16, 2021, at 1:02 PM, James Brown  wrote:
>
>
> There's been a lot of back and forth on the wider Internet and in this
> mailing list about whether incremental repairs are fatally flawed in
> Cassandra 3.x or whether they're still a good default. What's the current
> best thinking? The most recent 3.x documentation
>  still
> advocates in favor of using incremental repairs...
>
> CASSANDRA-9143  is
> marked as fixed in 4.0; did any improvements make it into any of the 3.11.x
> releases?
>
> If I need the performance of incremental repairs, should I just be
> plotting a 4.0.x upgrade?
>
> --
> James Brown
> Engineer
>
>
>

Re: state of incremental repairs in cassandra 3.x

[C. Scott Andreas]

Hi James, thanks for reaching out.A large number of fixes have landed for Incremental 
Repair in the 3.x series, though it's possible some may have been committed to 4.0 
without a backport. Incremental repair works well on Cassandra 4.0.1. I'd start here 
to ensure you're picking up all fixes that went in, though I do think it's likely to 
work well on a recent 3.0.x build as well (I'm less familiar with the 3.11.x 
series).– ScottOn Sep 16, 2021, at 1:02 PM, James Brown  
wrote:There's been a lot of back and forth on the wider Internet and in this mailing 
list about whether incremental repairs are fatally flawed in Cassandra 3.x or whether 
they're still a good default. What's the current best thinking? The most recent 3.x 
documentation still advocates in favor of using incremental repairs...CASSANDRA-9143 
is marked as fixed in 4.0; did any improvements make it into any of the 3.11.x 
releases?If I need the performance of incremental repairs, should I just be plotting 
a 4.0.x upgrade?-- James BrownEngineer

state of incremental repairs in cassandra 3.x

[James Brown]

There's been a lot of back and forth on the wider Internet and in this
mailing list about whether incremental repairs are fatally flawed in
Cassandra 3.x or whether they're still a good default. What's the current
best thinking? The most recent 3.x documentation
 still
advocates in favor of using incremental repairs...

CASSANDRA-9143  is
marked as fixed in 4.0; did any improvements make it into any of the 3.11.x
releases?

If I need the performance of incremental repairs, should I just be plotting
a 4.0.x upgrade?

-- 
James Brown
Engineer