Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.9.0
-
None
-
None
Description
I've been seen this in a cluster deployment as well as in UT, run TestAMRMClient#testAMRMClientWithContainerPromotion could reproduce this, it doesn't fail the test case but following error message is shown up in the log
2017-12-13 19:41:31,817 ERROR rmcontainer.RMContainerImpl (RMContainerImpl.java:handle(480)) - Can't handle this event at current state org.apache.hadoop.yarn.state.InvalidStateTransitionException: Invalid event: RELEASED at ALLOCATED at org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:305) at org.apache.hadoop.yarn.state.StateMachineFactory.access$500(StateMachineFactory.java:46) at org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:487) at org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl.handle(RMContainerImpl.java:478) at org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl.handle(RMContainerImpl.java:65) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.AbstractYarnScheduler.completedContainer(AbstractYarnScheduler.java:675) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:1586) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:155) at org.apache.hadoop.yarn.event.EventDispatcher$EventProcessor.run(EventDispatcher.java:66) at java.lang.Thread.run(Thread.java:748) 2017-12-13 19:41:31,817 ERROR rmcontainer.RMContainerImpl (RMContainerImpl.java:handle(481)) - Invalid event RELEASED on container container_1513165290804_0001_01_000003
this seems to be related to YARN-6251.
Attachments
Issue Links
- is related to
-
YARN-6251 Do async container release to prevent deadlock during container updates
- Resolved