[
https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600232#comment-13600232
]
Thomas Graves commented on YARN-460:
------------------------------------
Also note that I manually tested this by delaying the kill container message
going to AM and sleeping between when the app is marked done and before it was
removed from the application list. I was able to reproduce the issue, then
saw this patch fix it and the AM get the reboot command. I tested both
capacity scheduler and fifo.
> CS user left in list of active users for the queue even when application
> finished
> ---------------------------------------------------------------------------------
>
> Key: YARN-460
> URL: https://issues.apache.org/jira/browse/YARN-460
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 0.23.7, 2.0.4-alpha
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Priority: Critical
> Attachments: YARN-460-branch-0.23.patch, YARN-460-branch-0.23.patch,
> YARN-460.patch, YARN-460.patch, YARN-460.patch
>
>
> We have seen a user get left in the queues list of active users even though
> the application was removed. This can cause everyone else in the queue to get
> less resources if using the minimum user limit percent config.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
