[
https://issues.apache.org/jira/browse/CASSANDRA-21102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-21102:
--------------------------------------
Attachment: ci_summary-trunk-1d5021993e45748240e1a91959bdb8e5dcfdaa90.html
result_details-trunk-1d5021993e45748240e1a91959bdb8e5dcfdaa90.tar.gz
> Fix off-by-one bug in exponential backoff for repair retry config
> -----------------------------------------------------------------
>
> Key: CASSANDRA-21102
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21102
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Reporter: Nivy Kani
> Assignee: Nivy Kani
> Priority: Normal
> Fix For: 6.x
>
> Attachments:
> ci_summary-trunk-1d5021993e45748240e1a91959bdb8e5dcfdaa90.html,
> ci_summary.html,
> result_details-trunk-1d5021993e45748240e1a91959bdb8e5dcfdaa90.tar.gz,
> result_details.tar.gz
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The upper bound for repair retry backoff is multiplied by 2^attempts, but
> attempts always starts at 1. This means we always wait (at maximum) twice as
> long for the first retry attempt.
> Rather than modify the complex regex string defining retries, we can modify
> LatencyModifier to interpret this exponent as max(0, attempts - 1).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
