Hadoop Map/Reduce
  1. Hadoop Map/Reduce
  2. MAPREDUCE-3294

Log the reason for killing a task during speculative execution

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.23.0
    • Fix Version/s: 0.24.0
    • Component/s: mrv2
    • Labels:
      None

      Description

      The reason for killing a speculated task has to be logged. Currently, a speculated task is killed with a note of "Container killed by the ApplicationMaster. Container killed on request. Exit code is 137" which is not very useful. Better logging of this message stating the task was killed due to completion of its speculative task would be useful.

      Also, this message is lost once the app is moved to history. All we are left with is a list of killed tasks without a reason being notified to the user.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Ramya Sunil
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development