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

Exception thrown in/from RecoveryManager.recover() should be caught and handled

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

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 0.20.0
    • 0.19.2, 0.20.0
    • None
    • None
    • Reviewed

    Description

      RecoveryManager.recover() can throw an exception while recovering a job. Since the JobTracker calls RecoveryManager.recover() from offerService(), any failure in recovery will cause JobTracker to crash. Ideally the RecoveryManager should log the failure encountered while recovering the job and continue.

      Attachments

        1. HADOOP-4638-v1.8.5.patch
          12 kB
          Amar Kamat
        2. HADOOP-4638-v1.8.patch
          14 kB
          Amar Kamat
        3. HADOOP-4638-v1.6.patch
          13 kB
          Amar Kamat
        4. HADOOP-4638-v1.3.patch
          13 kB
          Amar Kamat
        5. HADOOP-4638-v1.1.patch
          12 kB
          Amar Kamat

        Activity

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

          People

            amar_kamat Amar Kamat
            amar_kamat Amar Kamat
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment