You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2021/09/17 22:20:00 UTC
[jira] [Updated] (CASSANDRA-16968) Diff Job retry bug fixes in
reading previous run's job parameters & marking the job status
[ https://issues.apache.org/jira/browse/CASSANDRA-16968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-16968:
-----------------------------------------
Change Category: Operability
Complexity: Normal
Component/s: Tool/diff
Status: Open (was: Triage Needed)
> Diff Job retry bug fixes in reading previous run's job parameters & marking the job status
> ------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16968
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16968
> Project: Cassandra
> Issue Type: New Feature
> Components: Tool/diff
> Reporter: Jyothsna Konisa
> Assignee: Jyothsna Konisa
> Priority: Normal
>
> Diff job retry with same jobId should avoid running diffs on the partitions that were successfully diffed previously. The retry failed because previous run failed to mark the job as not running on exit. This is due to a bug in the resource try catch block where session object Is closed before marking the job as not running. Also there is another bug in the way we get job parameters during rerun of a failed diff job.
--
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