[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 ] Yifan Cai updated CASSANDRA-16211: -- Source Control Link: https://github.com/apache/cassandra-diff/commit/e3161b60b78b5cfbeba4875acbbb2f138d5da051 Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed as [e3161b6|https://github.com/apache/cassandra-diff/commit/e3161b60b78b5cfbeba4875acbbb2f138d5da051] > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Dinesh Joshi updated CASSANDRA-16211: - Status: Ready to Commit (was: Review In Progress) > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Yifan Cai updated CASSANDRA-16211: -- Reviewers: Dinesh Joshi Status: Review In Progress (was: Patch Available) > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] ASF GitHub Bot updated CASSANDRA-16211: --- Labels: pull-request-available (was: ) > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[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 ] Yifan Cai updated CASSANDRA-16211: -- Test and Documentation Plan: unit test Status: Patch Available (was: Open) 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 > > 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
[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 ] 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
