Hadoop Common
  1. Hadoop Common
  2. HADOOP-588

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

    Details

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

      Description

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

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

        Activity

        Hide
        Doug Cutting added a comment -

        I just committed this. Thanks, Sanjay!

        Show
        Doug Cutting added a comment - I just committed this. Thanks, Sanjay!
        Hide
        Owen O'Malley added a comment -

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

        Show
        Owen O'Malley added a comment - I think that we should push this to 0.8.0 since it is not a stability issue.
        Hide
        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.

        Show
        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.
        Hide
        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.

        Show
        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.

          People

          • Assignee:
            Sanjay Dahiya
            Reporter:
            Sanjay Dahiya
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development