[
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-20121109.txt
Address Bobby's comments on my earlier patch.
- Agree about Hashset. Started doing bitmaps, but it made code unreadable.
Keeping HashSet but with an explicit initial capacity of 2 instead of the
default 16. Could've been 1, but HashSet/HashMap immediately resizes it to two.
- Addressed other changes.
- Wrote up a test which passes with the changes and fails without. Had to
spend a lot of time to get it right.
> 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,
> MAPREDUCE-4751-20121109.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
