[ https://issues.apache.org/jira/browse/CASSANDRA-18466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-18466: ----------------------------------------- Fix Version/s: 4.1.4 5.0 5.1 (was: 5.x) (was: 4.1.x) (was: 5.0.x) Since Version: 4.1.0 Source Control Link: https://github.com/apache/cassandra/commit/725655dda2776fef35567496a6e331102eb7610d Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed, thanks folks! > 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 > Assignee: Ningzi Zhan > Priority: Normal > Labels: lhf > Fix For: 4.1.4, 5.0, 5.1 > > Time Spent: 40m > Remaining Estimate: 0h > > 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