[ 
https://issues.apache.org/jira/browse/CASSANDRA-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yifan Cai updated CASSANDRA-16211:
----------------------------------
    Change Category: Operability
         Complexity: Low Hanging Fruit
             Status: Open  (was: Triage Needed)

> 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
>
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to