[
https://issues.apache.org/jira/browse/CASSANDRA-20430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Tolbert updated CASSANDRA-20430:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Triage Needed)
Looks like this got merged into trunk_cep_37 in
[88dd2d5|https://github.com/apache/cassandra/pull/3598/commits/88dd2d509d0230f162be6fd845d7900e2cb38545]
so resolving this out.
> Auto-repair retries should be configurable at repair type level
> ---------------------------------------------------------------
>
> Key: CASSANDRA-20430
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20430
> Project: Apache Cassandra
> Issue Type: Bug
> Reporter: Kristijonas Zalys
> Assignee: Kristijonas Zalys
> Priority: Normal
>
> The auto-repair scheduler allows configuring how many times a given repair
> command is retried and the backoff period between retries. However, these are
> global settings that apply to all supported repair types, based on my
> experience this is not sufficient.
> Retrying incremental repair usually ends up simply slowing down incremental
> repair. It's best to allow incremental repair to simply fail and retry the
> failed repair command during the next repair cycle. This means that retries
> should be disabled for incremental repair.
> However, the repair interval for full repair would generally be much larger
> than incremental repair. As a result, it is not a good idea to wait for the
> next repair cycle to retry full repair. For full repair it is best to retry
> repair immediately. This means that incremental and full repair would require
> separate retry policies.
>
--
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
