[ https://issues.apache.org/jira/browse/CASSANDRA-18466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-18466: ----------------------------------------- Bug Category: Parent values: Correctness(12982) Complexity: Normal Component/s: Consistency/Repair Discovered By: User Report Fix Version/s: 4.1.x 5.x Severity: Normal Status: Open (was: Triage Needed) > Paxos only repair is treated as an incremental repair > ----------------------------------------------------- > > Key: CASSANDRA-18466 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18466 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Repair > Reporter: Andrew > Priority: Normal > Fix For: 4.1.x, 5.x > > > Paxos only repair tries to continue or is treated as an incremental repair. > This happened on 4.1.0 and 4.1.1 when trying to run repair in preparation for > enabling paxos_state_purging. The repair was in preparation mode triggered > multiple anti-compactions on the nodes. Running the command with --full > behaves in the expected way, ie. only the paxos data is repaired and it's > finished within a few seconds. > {code:java} > nodetool repair --paxos-only // This does not behave as expected, does it > complete quickly and seems to be waiting on anticompactions > {code} > {code:java} > nodetool repair --full --paxos-only // Completes within a few seconds as > expected > {code} -- 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