Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-5746

Job diagnostics can implicate wrong task for a failed job

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.23.10, 2.1.1-beta
    • 0.23.11, 2.4.0
    • jobhistoryserver
    • None

    Description

      We've seen a number of cases where the history server is showing the wrong task as the reason a job failed. For example, "Task task_1383802699973_515536_m_027135 failed 1 times" when some other task had failed 4 times and was the real reason the job failed.

      Attachments

        1. MAPREDUCE-5746.patch
          1 kB
          Jason Darrell Lowe
        2. MAPREDUCE-5746-v2.branch-0.23.patch
          5 kB
          Jason Darrell Lowe
        3. MAPREDUCE-5746-v2.patch
          5 kB
          Jason Darrell Lowe

        Issue Links

        is related to

        Improvement - An improvement or enhancement to an existing feature or task. MAPREDUCE-5754 Preserve Job diagnostics in history

        • Major - Major loss of function.
        • Closed
        relates to

        Bug - A problem which impairs or prevents the functions of the product. MAPREDUCE-5317 Stale files left behind for failed jobs

        • Major - Major loss of function.
        • Closed

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

          People

            jlowe Jason Darrell Lowe
            jlowe Jason Darrell Lowe
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment