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

Daniel Templeton commented on YARN-5136:
----------------------------------------

Thanks for the patch.  It looks to me like it might be better to throw a 
{{YarnException}} in {{moveApplication()}} rather than just returning the 
current queue's name.  The exception gets swallowed by the transition, so it 
shouldn't hurt anything, and it feels like the more natural path, rather than 
pretending that everything's OK.  Also your tests don't explicitly test 
anything.  I get that you're just seeing if the operation blows up, but it 
would be nice to do some additional confirmation, like that the app is still in 
the original queue.

> Error in handling event type APP_ATTEMPT_REMOVED to the scheduler
> -----------------------------------------------------------------
>
>                 Key: YARN-5136
>                 URL: https://issues.apache.org/jira/browse/YARN-5136
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.1
>            Reporter: tangshangwen
>            Assignee: Wilfred Spiegelenburg
>         Attachments: YARN-5136.1.patch
>
>
> move app cause rm exit
> {noformat}
> 2016-05-24 23:20:47,202 FATAL 
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error in 
> handling event type APP_ATTEMPT_REMOVED to the scheduler
> java.lang.IllegalStateException: Given app to remove 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSAppAttempt@ea94c3b
>  does not exist in queue [root.bdp_xx.bdp_mart_xx_formal, 
> demand=<memory:28672000, vCores:14000>, running=<memory:28647424, 
> vCores:13422>, share=<memory:28672000, vCores:0>, w=<memory weight=1.0, cpu 
> weight=1.0>]
>     at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FSLeafQueue.removeApp(FSLeafQueue.java:119)
>     at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.removeApplicationAttempt(FairScheduler.java:779)
>     at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:1231)
>     at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:114)
>     at 
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:680)
>     at java.lang.Thread.run(Thread.java:745)
> 2016-05-24 23:20:47,202 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmcontainer.RMContainerImpl: 
> container_e04_1464073905025_15410_01_001759 Container Transitioned from 
> ACQUIRED to RELEASED
> 2016-05-24 23:20:47,202 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Exiting, bbye..
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to