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

Jason Lowe commented on YARN-2176:
----------------------------------

Sure, that works if we think that's cleaner.  It's a little weird that 
AppSchedulingInfo is already calling back into an object obtained from the 
queue to notify of app activation state (i.e.: the ActiveUsersManager instance) 
and then we'd register a second object from the same queue to receive the same 
events.  IMHO it'd be nice to not have two separate paths to tell the queue 
about the same thing.

> CapacityScheduler loops over all running applications rather than actively 
> requesting apps
> ------------------------------------------------------------------------------------------
>
>                 Key: YARN-2176
>                 URL: https://issues.apache.org/jira/browse/YARN-2176
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>    Affects Versions: 2.4.0
>            Reporter: Jason Lowe
>
> The capacity scheduler performance is primarily dominated by 
> LeafQueue.assignContainers, and that currently loops over all applications 
> that are running in the queue.  It would be more efficient if we looped over 
> just the applications that are actively asking for resources rather than all 
> applications, as there could be thousands of applications running but only a 
> few hundred that are currently asking for resources.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to