Uploaded image for project: 'Apache Helix'
  1. Apache Helix
  2. HELIX-618

Job hung if the target resource does not exist anymore at the time when it is scheduled.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              andrewlxia Lei Xia
              Reporter:
              andrewlxia Lei Xia
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: