[
https://issues.apache.org/jira/browse/MAPREDUCE-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159842#comment-13159842
]
Ramgopal N commented on MAPREDUCE-3339:
---------------------------------------
Have only one NM. Submit a big job and continuosly kill the child processes on
that NM. After some time NM will stop respawning the child proceeses and the
job is also hanged.And nowhere in the logs it is given as blacklisted.
> Job is getting hanged indefinitely,if the child processes are killed on the
> NM. KILL_CONTAINER eventtype is continuosly sent to the containers that are
> not existing
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3339
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3339
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.23.0
> Reporter: Ramgopal N
> Assignee: Siddharth Seth
> Priority: Blocker
>
> I have only one NM running.
> I have submitted a job and all the child processes on the NM got killed
> continuosly.This made the Job to hang indefinitely.
> In the NM logs it is logging WARN message
> :org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl:
> Event EventType: KILL_CONTAINER sent to absent container
> container_1320301910500_0004_01_001359
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
