You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (Jira)" <ji...@apache.org> on 2021/03/19 11:25:00 UTC
[jira] [Updated] (CASSANDRA-16211) Improve job metadata queries
exception handling in cassandra-diff
[ https://issues.apache.org/jira/browse/CASSANDRA-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Lerer updated CASSANDRA-16211:
---------------------------------------
Fix Version/s: 4.0.x
> 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
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org