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

[jira] [Commented] (HELIX-784) TASK: Fix a bug in getExpiredJobs

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

Hudson commented on HELIX-784:
------------------------------

FAILURE: Integrated in Jenkins build helix #1566 (See [https://builds.apache.org/job/helix/1566/])
[HELIX-784] TASK: Fix a bug in getExpiredJobs (narendly: rev befb1036f8d8be2729a800d3dde88fc1362a6489)
* (delete) helix-core/src/test/java/org/apache/helix/controller/stages/TestTaskPersistDataStage.java
* (add) helix-core/src/test/java/org/apache/helix/controller/stages/TestTaskStage.java
* (edit) helix-core/src/main/java/org/apache/helix/task/TaskUtil.java


> TASK: Fix a bug in getExpiredJobs
> ---------------------------------
>
>                 Key: HELIX-784
>                 URL: https://issues.apache.org/jira/browse/HELIX-784
>             Project: Apache Helix
>          Issue Type: Improvement
>            Reporter: Hunter L
>            Assignee: Hunter L
>            Priority: Major
>
> getExpiredJobs(), when the job config is null, would just continue instead of adding it to expiredJobs so that the job cleanup/purge would be re-tried. This could possibly cause purge failures to leave a lot of jobs un-purged with just the job config missing in ZK. This RB fixes this.
> Changelist:
> 1. Add the job name to expiredJobs if the job config does not exist in ZK
> 2. Add a more detailed description in the error log
> 3. Add an integration test for two task-related stages: TaskPersistDataStage and TaskGarbageCollectionStage in TestTaskStage.java



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