[
https://issues.apache.org/jira/browse/CASSANDRA-16125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yifan Cai updated CASSANDRA-16125:
----------------------------------
Test and Documentation Plan: unit test
Status: Patch Available (was: Open)
PR: [https://github.com/apache/cassandra-diff/pull/12]
* Retry at the application level.
* Added 2 strategies in the PR, {{NoRetry}} and {{ExponentialRetry}}.
* {{RetryStrategy}} is made pluggable, as long as that the custom
implementation extends the base and specify it in the config. Therefore, the
constructor takes a map that is read from config.
* {{NoRetry}} is used if no {{RetryOptions}} is supplied in the config.
The {{ExponentialRetry}} takes 2 parameters, base and total delay in
milliseconds. Each time when retry is permitted, the paused time is increased
exponentially. When the total time from the past pauses exceeds the specified
{{totalDelayMs}}, the retry strategy no longer permits more retries.
> Allow optional query retry in cassandra-diff
> --------------------------------------------
>
> Key: CASSANDRA-16125
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16125
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/diff
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Normal
>
> The diff job fails when seeing the first query timeout/unavailable.
> We can add an optional retry policy to add the spark workers retry the failed
> query for a maximum amount of duration (i.e. retry timeout).
> When the retry policy is set, the job only fails after the retry timeout
> exceeds.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
