[
https://issues.apache.org/jira/browse/YARN-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618043#comment-13618043
]
Hudson commented on YARN-460:
-----------------------------
Integrated in Hadoop-Yarn-trunk #170 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/170/])
YARN-460. CS user left in list of active users for the queue even when
application finished (tgraves) (Revision 1462486)
Result = FAILURE
tgraves :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1462486
Files :
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/fica/FiCaSchedulerApp.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
> 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: Blocker
> Fix For: 3.0.0, 0.23.7, 2.0.5-beta
>
> Attachments: YARN-460-branch-0.23.patch, YARN-460-branch-0.23.patch,
> YARN-460-branch-0.23.patch, YARN-460.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
