Thanks everyone for your helpful feedback! I've updated my blog post to
hopefully reflect these clarifications:
https://msun.io/cassandra-scylla-repairs/
<https://msun.io/cassandra-scylla-repairs/index.html>
On Mon, May 19, 2025 at 9:27 AM Mike Sun wrote:
> To simplify operati
Jaydeep. It will
definitely make it easier for operators to monitor and alarm on potential
expiring tombstone risks. I will update my post to include this upcoming
feature.
Best,
Mike Sun
On Sat, May 17, 2025 at 12:54 PM Mike Sun wrote:
>
>> Jeremiah, you’re right, I’ve been using “re
will have been repaired
> within 7 days, even though the start of repair 1 to the finish of repair 2
> was more than 7 days. The start of “token ranges repaired on day 0” to the
> finish of “token ranges repaired on day 7” is less than the gc_grace window.
>
> -Jeremiah Jordan
>
>
two consecutive repairs within gc_grace_seconds"
On Fri, May 16, 2025 at 2:49 PM Mike Sun wrote:
> > You need to *start and complete* a repair within any gc_grace_seconds
> window.
> Exactly this. And since "any gc_grace_seconds" does not mean "any
> gc_grace_window from
> You need to *start and complete* a repair within any gc_grace_seconds
window.
Exactly this. And since "any gc_grace_seconds" does not mean "any
gc_grace_window from which a repair starts"... the requirement needs to be
that the duration to "start and complete" two consecutive full repairs is
with
an be
circumstances that could cause repairs to be paused or stopped for periods
of times (e.g. adding new nodes to cluster). FWIW, full repairs taking 3
days is was not uncommon thing in my experience.
On Fri, May 16, 2025 at 1:57 PM Jeff Jirsa wrote:
>
>
> On May 16, 2025, at 10:2
a resurrection.
I wrote this post to explain my reasoning:
https://msun.io/cassandra-scylla-repairs/
<https://msun.io/cassandra-scylla-repairs/>
Would appreciate any feedback, thanks!
Mike Sun
