hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5269) TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever in some cases.
Date Wed, 18 Feb 2009 08:57:01 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hemanth Yamijala updated HADOOP-5269:
-------------------------------------

    Fix Version/s: 0.20.0

> TaskTracker.runningTasks holding FAILED_UNCLEAN and KILLED_UNCLEAN taskStatuses forever
in some cases.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5269
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5269
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.1
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amareshwari Sriramadasu
>            Priority: Blocker
>             Fix For: 0.19.1, 0.20.0
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message