You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Blake Eggleston (Jira)" <ji...@apache.org> on 2026/01/20 23:05:00 UTC

[jira] [Commented] (CASSANDRA-21098) CEP-45: Incremental repair for mutation tracking

    [ https://issues.apache.org/jira/browse/CASSANDRA-21098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053164#comment-18053164 ] 

Blake Eggleston commented on CASSANDRA-21098:
---------------------------------------------

PR: https://github.com/apache/cassandra/pull/4569

> CEP-45: Incremental repair for mutation tracking
> ------------------------------------------------
>
>                 Key: CASSANDRA-21098
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21098
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Consistency/Repair
>            Reporter: Blake Eggleston
>            Assignee: Aparna Naik
>            Priority: Normal
>
> Incremental repair should block until all writes issued before the repair start are fully replicated. Although mutation tracking propagates this asynchronously, we need a mechanism to wait for completion.
> In this ticket we build a SyncMechanism that would be collecting mutation offsets from all replicas for relevant shards, compute their union and wait until all these replicas report having received them. The repair command will be extended to support this for keyspaces using mutation tracking. During shard migrations in either direction, incremental repair should perform both mutation-tracking and data repairs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org