Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 13 Dec 2017 13:08:00 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13124653.1513166565000.448691.1513170480428@Atlassian.JIRA>
In-Reply-To: <JIRA.13124653.1513166565000@Atlassian.JIRA>
References: <JIRA.13124653.1513166565000@Atlassian.JIRA> <JIRA.13124653.1513166565973@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (YARN-7649) RMContainer state transition
 exception after container update
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 13 Dec 2017 13:08:08 -0000


    [ https://issues.apache.org/jira/browse/YARN-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289229#comment-16289229 ] 

Arun Suresh edited comment on YARN-7649 at 12/13/17 1:07 PM:
-------------------------------------------------------------

Thanks for raising [~cheersyang]. Yeah. We have a patch for this internally. Assigning it to myself


was (Author: asuresh):
Yeah. We have a patch for this internally. Assigning it to myself

> RMContainer state transition exception after container update
> -------------------------------------------------------------
>
>                 Key: YARN-7649
>                 URL: https://issues.apache.org/jira/browse/YARN-7649
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.9.0
>            Reporter: Weiwei Yang
>            Assignee: Arun Suresh
>
> 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
> {noformat}
> 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
> {noformat}
> this seems to be related to YARN-6251.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org