[
https://issues.apache.org/jira/browse/CASSANDRA-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214875#comment-17214875
]
Yifan Cai edited comment on CASSANDRA-16211 at 5/6/21, 9:41 PM:
----------------------------------------------------------------
PR:
[https://github.com/apache/cassandra-diff/pull/15|https://github.com/apache/cassandra-diff/pull/15]
The patch does what mentioned in the description.
* Ignore query exceptions from queries in ProgressTracker
* Retry (when a retry strategy is specified) queries in JobLifeCycle
was (Author: yifanc):
PR: [https://github.com/apache/cassandra-diff/pull/13]
The patch does what mentioned in the description.
* Ignore query exceptions from queries in ProgressTracker
* Retry (when a retry strategy is specified) queries in JobLifeCycle
> Improve job metadata queries exception handling in cassandra-diff
> -----------------------------------------------------------------
>
> Key: CASSANDRA-16211
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16211
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/diff
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Normal
> Labels: pull-request-available
> Fix For: 4.0.x
>
>
> The job metadata tracks the progress of the diff job. Sometimes, a job can
> fail due to the progress update query failures.
> The progress update queries can be categorized into 2 groups, critical and
> trivial one.
> When a query failed to update a trivial status (e.g. ProgressTracker), we
> would mostly hope to continue the job and just log the failure.
> When a query failed to update a critical status (e.g. JobLifeCycle), we can
> apply the client-side retry strategy (e.g. exponential backoff) in addition
> to the retry policy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
