helix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lei Xia (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (HELIX-618) Job hung if the target resource does not exist anymore at the time when it is scheduled.
Date Fri, 26 Aug 2016 22:45:20 GMT

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

Lei Xia closed HELIX-618.
-------------------------
    Resolution: Fixed

>  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.3.4#6332)

Mime
View raw message