You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Sharad Agarwal (JIRA)" <ji...@apache.org> on 2011/08/24 10:46:29 UTC
[jira] [Created] (MAPREDUCE-2875) NM does not communicate Container
crash to RM
NM does not communicate Container crash to RM
---------------------------------------------
Key: MAPREDUCE-2875
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2875
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Sharad Agarwal
Fix For: 0.23.0
Faulty container crash detection code path in NodeManager.
Steps:
Run a job.
Kill the AM container in NM.
NM logs has:
org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: CONTAINER_KILLED_ON_REQUEST at RUNNING
at org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:297)
at org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:39)
at org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:439)
at org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:685)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MAPREDUCE-2875) NM does not communicate
Container crash to RM
Posted by "Vinod Kumar Vavilapalli (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli resolved MAPREDUCE-2875.
------------------------------------------------
Resolution: Duplicate
Assignee: Siddharth Seth (was: Devaraj K)
Sid fixed the same via MAPREDUCE-3031. Closing this as duplicate.
> NM does not communicate Container crash to RM
> ---------------------------------------------
>
> Key: MAPREDUCE-2875
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2875
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Sharad Agarwal
> Assignee: Siddharth Seth
> Fix For: 0.23.0
>
>
> Faulty container crash detection code path in NodeManager.
> Steps:
> Run a job.
> Kill the AM container in NM.
> NM logs has:
> org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: CONTAINER_KILLED_ON_REQUEST at RUNNING
> at org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:297)
> at org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:39)
> at org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:439)
> at org.apache.hadoop.yarn.server.nodemanager.containermanager.container.ContainerImpl.handle(ContainerImpl.java:685)
--
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