You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@helix.apache.org by "Hunter L (JIRA)" <ji...@apache.org> on 2018/11/01 23:58:00 UTC

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

Hunter L created HELIX-784:
------------------------------

             Summary: 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


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)