[
https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597237#comment-13597237
]
Thomas Graves commented on YARN-460:
------------------------------------
Just for reference the RM log shows the application removed:
2013-02-27 06:59:50,390 [ResourceManager Event Processor] INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue:
Application removed - appId: application_1360172387725_270658 user: userfoo
queue: adhoc #user-pending-applications: 0 #user-active-applications: 5
#queue-pending-applications: 0 #queue-active-applications: 25
Unfortunately the allocate call only logs at DEBUG level and we are at INFO
level.
> 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
>
> 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
