[
https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597281#comment-13597281
]
Thomas Graves commented on YARN-460:
------------------------------------
Note that this is due to the fact that CapacityScheduler.allocate() call is not
synchronized like other calls so the capacity scheduler thread can be calling
doneApplication at the same time the allocate call comes in. This means that
allocate can be looking at/updating the SchedulerApp while its being stopped.
We need a way to either synchronize on the SchdulerApp itself or perhaps have
the calls into SchedulerApp check to make sure its hasn't been stopped.
> 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
