[
https://issues.apache.org/jira/browse/HELIX-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16298817#comment-16298817
]
Hudson commented on HELIX-618:
------------------------------
FAILURE: Integrated in Jenkins build helix #1383 (See
[https://builds.apache.org/job/helix/1383/])
[HELIX-618] Job hung if the target resource does not exist anymore at (jxue:
rev 79f94cedae2dca5f57113bc80f7cd1af91b0ce31)
* (edit) helix-core/src/main/java/org/apache/helix/task/WorkflowRebalancer.java
* (add)
helix-core/src/test/java/org/apache/helix/integration/task/TestRunJobsWithMissingTarget.java
* (edit) helix-core/src/main/java/org/apache/helix/task/JobRebalancer.java
* (edit) helix-core/src/main/java/org/apache/helix/task/TaskRebalancer.java
* (edit)
helix-core/src/main/java/org/apache/helix/task/FixedTargetTaskAssignmentCalculator.java
> Job hung if the target resource does not exist anymore at the time when it
> is scheduled.
> -----------------------------------------------------------------------------------------
>
> Key: HELIX-618
> URL: https://issues.apache.org/jira/browse/HELIX-618
> Project: Apache Helix
> Issue Type: Bug
> Reporter: Lei Xia
> Assignee: Lei Xia
>
> When the job gets scheduled, if the target resource does not exist any more
> (for example, database already deleted but the backup job is still there),
> the job is stuck and all the rest of jobs in the same workflow are stuck.
> Solution:
> If the target resource of a job does not exist, the job should be failed
> immediately. And depends on the queue configuration, the rest of jobs will
> either continue to run, or the queue will be marked as failed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
