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

TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.19.1
    • Fix Version/s: 0.19.2, 0.20.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Tasktracker is holdingup TaskStatus objects in runningTasks forever in somecases. This happens in the following scenario.
      -> Task got an exception
      -> Sets the phase to CLEANUP
      -> The task tries to do cleanup. and it doesn't respond after that.
      -> TaskTracker marks the task unresponsive and makes the task FAILED_UNCLEAN
      -> TaskTracker doesn't remove it from runningTasks data structure, since phase is CLEANUP and state is FAILED_UNCLEAN (it treats this as cleanupAttempt).

      I would propose that once the task goes to CLEANUP phase, kill on the task should mark it a clean failure i.e. The task state should be FAILED/KILLED.

        Attachments

        1. patch-5269.txt
          11 kB
          Amareshwari Sriramadasu
        2. patch-5269-0.19-0.20.txt
          10 kB
          Amareshwari Sriramadasu

          Activity

            People

            • Assignee:
              amareshwari Amareshwari Sriramadasu
              Reporter:
              amareshwari Amareshwari Sriramadasu
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: