Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-4053

Schedulers need to know when a job has completed

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 0.19.0
    • 0.19.0
    • None
    • None
    • Reviewed

    Description

      The JobInProgressListener interface is used by the framework to notify Schedulers of when jobs are added, removed, or updated. Right now, there is no way for the Scheduler to know that a job has completed. jobRemoved() is called when a job is retired, which can happen many hours after a job is actually completed. jobUpdated() is called when a job's priority is changed. We need to notify a listener when a job has completed (either successfully, or has failed or been killed).

      Attachments

        1. HADOOP-4053-v1.patch
          4 kB
          Amar Kamat
        2. HADOOP-4053-v2.patch
          7 kB
          Amar Kamat
        3. HADOOP-4053-v3.1.patch
          21 kB
          Amar Kamat
        4. HADOOP-4053-v3.2.patch
          20 kB
          Amar Kamat
        5. HADOOP-4053-v4.1.patch
          26 kB
          Amar Kamat
        6. HADOOP-4053-v4.patch
          24 kB
          Amar Kamat
        7. HADOOP-4053-v5.2.patch
          37 kB
          Amar Kamat
        8. HADOOP-4053-v5.3.patch
          37 kB
          Amar Kamat
        9. HADOOP-4053-v5.4.patch
          45 kB
          Amar Kamat
        10. HADOOP-4053-v5.5.patch
          48 kB
          Amar Kamat

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            amar_kamat Amar Kamat
            vivekr Vivek Ratan
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment