[
https://issues.apache.org/jira/browse/HELIX-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554970#comment-16554970
]
Hudson commented on HELIX-746:
------------------------------
FAILURE: Integrated in Jenkins build helix #1527 (See
[https://builds.apache.org/job/helix/1527/])
[HELIX-746] Fix removeJob so its behavior is more consistent with (narendly:
rev ae23842d24409e26c67f5c99113762bd0eb714b0)
* (edit) helix-core/src/main/java/org/apache/helix/task/TaskUtil.java
> [TASK] Fix removeJob so its behavior is more consistent with removeWorkflow
> ---------------------------------------------------------------------------
>
> Key: HELIX-746
> URL: https://issues.apache.org/jira/browse/HELIX-746
> Project: Apache Helix
> Issue Type: Improvement
> Reporter: Hunter L
> Priority: Major
>
> Change the behavior of removeJob() so that it's more consistent with
> removeWorkflow(). This RB addresses the scenario: suppose config deletion
> failed (so config still exists) and context deletion succeeded. Then the
> Controller has no way of knowing whether this job has ever been scheduled or
> it was meant to be deleted (although failed due to partial deletion).
> Returning as soon as config deletion fails can prevent this scenario.
> Changelist:
> 1. Make removeJob() return early as soon as a ZNode write failure is detected
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
