[ https://issues.apache.org/jira/browse/CASSANDRA-20597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17947255#comment-17947255 ]
Jaydeepkumar Chovatia commented on CASSANDRA-20597: --------------------------------------------------- Yeah, I agree that _--paxos-only_ is already available. This ticket is a proposal to extend the CEP-37 work by having Paxos repair as a separate repair type as part of managed repair work. The CEP-37, as of today, offers the following [three repair types|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/repair/autorepair/AutoRepairConfig.java#L97]: 1) FULL, 2) INCREMENTAL, and 3) PREVIEW_REPAIRED This ticket suggests introducing the 4th type, PAXOS, in the context of the CEP-37 managed repair solution. > Introduce Paxos repair as a separate repair type > ------------------------------------------------ > > Key: CASSANDRA-20597 > URL: https://issues.apache.org/jira/browse/CASSANDRA-20597 > Project: Apache Cassandra > Issue Type: Task > Components: Consistency/Repair > Reporter: Jaydeepkumar Chovatia > Assignee: Jaydeepkumar Chovatia > Priority: Normal > > Paxos repair can be run as part of the incremental repair cycle by providing > the "repairPaxos" flag. > However, having Paxos repair as a separate repair type might be a good idea, > similar to "full", "incremental", and "preview_repair" in the context of the > CEP-37 managed repair solution. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org