You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/07/24 21:36:00 UTC

[jira] [Commented] (HELIX-743) [TASK] Fix purgeExpiredJobs() so that jobs whose removal has failed do not get removed from DAG

    [ https://issues.apache.org/jira/browse/HELIX-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554826#comment-16554826 ] 

Hudson commented on HELIX-743:
------------------------------

FAILURE: Integrated in Jenkins build helix #1525 (See [https://builds.apache.org/job/helix/1525/])
[HELIX-743] Fix purgeExpiredJobs() so that jobs whose removal has failed (narendly: rev c012c7b9dea35137935ac29c035a96aea570bf9c)
* (edit) helix-core/src/main/java/org/apache/helix/task/WorkflowRebalancer.java


> [TASK] Fix purgeExpiredJobs() so that jobs whose removal has failed do not get removed from DAG
> -----------------------------------------------------------------------------------------------
>
>                 Key: HELIX-743
>                 URL: https://issues.apache.org/jira/browse/HELIX-743
>             Project: Apache Helix
>          Issue Type: Improvement
>            Reporter: Hunter L
>            Priority: Major
>
> Previously, even if the job removal had failed, Task Framework would go ahead and remove the job from the DAG. This would cause some ZNodes to be left over and never be cleaned up at next purge time. Changelist: 1. Keep track of jobs whose removal failed and remove them from expiredJobs so that next call to purgeExpiredJobs(), the job would be included in expiredJobs again and removal would be tried again.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)