[
https://issues.apache.org/jira/browse/MAPREDUCE-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-4751:
-----------------------------------------------
Attachment: MAPREDUCE-4751-20121108.txt
Here's a first attempt for the patch. Very raw, no tests yet. Want to be sure
that I am understanding your comments correctly.
Bobby/Ravi/Jason, can you please have a quick look at it please? Tx.
I get a feeling we need to do something similar in Job also. Even though it
will not be the current bug assuming TaskImpl itself is stuck today.
> AM stuck in KILL_WAIT for days
> ------------------------------
>
> Key: MAPREDUCE-4751
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4751
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.23.3, 2.0.2-alpha
> Reporter: Ravi Prakash
> Assignee: Vinod Kumar Vavilapalli
> Attachments: MAPREDUCE-4751-20121108.txt, TaskAttemptStateGraph.jpg
>
>
> We found some jobs were stuck in KILL_WAIT for days on end. The RM shows them
> as RUNNING. When you go to the AM, it shows it in the KILL_WAIT state, and a
> few maps running. All these maps were scheduled on nodes which are now in the
> RM's Lost nodes list. The running maps are in the FAIL_CONTAINER_CLEANUP state
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
