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

JobTracker History bug - kill() ed tasks are logged wrongly as finished.

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.7.0
    • 0.8.0
    • None
    • None

    Description

      JobInProgress.kill() logs jobs as finished in jobtracker history, whereas they should be logged as failed.

      Attachments

        1. Hadoop-588.patch
          2 kB
          Sanjay Dahiya
        2. Hadoop-588-extra.patch
          1.0 kB
          Sanjay Dahiya

        Activity

          sanjay.dahiya Sanjay Dahiya added a comment -

          This patch fixes 2 issues with jobtracker history logging.
          1. JobInProgress.kill() now logs jobs as failed instead of finished.
          2. For failed task attempts, the failure is not propagated to Task page until the taskAttempts fails max(4) no of times. Earlier the failed task attempt's error would be visible on task page even when a subsequent task attempt succeeded, which was confusing.

          sanjay.dahiya Sanjay Dahiya added a comment - This patch fixes 2 issues with jobtracker history logging. 1. JobInProgress.kill() now logs jobs as failed instead of finished. 2. For failed task attempts, the failure is not propagated to Task page until the taskAttempts fails max(4) no of times. Earlier the failed task attempt's error would be visible on task page even when a subsequent task attempt succeeded, which was confusing.
          sanjay.dahiya Sanjay Dahiya added a comment -

          Submitting one more patch related to history with this bug ID.
          With this patch analyze history on WI will not attempt to analyze in case job did not succeed.

          note: it doesnt replace the existing patch, its in addition to that.

          sanjay.dahiya Sanjay Dahiya added a comment - Submitting one more patch related to history with this bug ID. With this patch analyze history on WI will not attempt to analyze in case job did not succeed. note: it doesnt replace the existing patch, its in addition to that.
          omalley Owen O'Malley added a comment -

          I think that we should push this to 0.8.0 since it is not a stability issue.

          omalley Owen O'Malley added a comment - I think that we should push this to 0.8.0 since it is not a stability issue.
          cutting Doug Cutting added a comment -

          I just committed this. Thanks, Sanjay!

          cutting Doug Cutting added a comment - I just committed this. Thanks, Sanjay!

          People

            sanjay.dahiya Sanjay Dahiya
            sanjay.dahiya Sanjay Dahiya
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: