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

Karthik Kambatla commented on YARN-3547:
----------------------------------------

+1, pending Jenkins.

At commit time, I plan to add the following comment: "Note that we might 
consider a non-runnable app for scheduling if it was just removed from 
runnableApps. This should be okay in practice - (1) because that is rare, and 
(2) holding the lock to disallow that doesn't alter the reality where 
conditions for an app to be made non-runnable have already been met."



> FairScheduler: Apps that have no resource demand should not participate 
> scheduling
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-3547
>                 URL: https://issues.apache.org/jira/browse/YARN-3547
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler
>            Reporter: Xianyin Xin
>            Assignee: Xianyin Xin
>         Attachments: YARN-3547.001.patch, YARN-3547.002.patch, 
> YARN-3547.003.patch, YARN-3547.004.patch, YARN-3547.005.patch, 
> YARN-3547.006.patch
>
>
> At present, all of the 'running' apps participate the scheduling process, 
> however, most of them may have no resource demand on a production cluster, as 
> the app's status is running other than waiting for resource at the most of 
> the app's lifetime. It's not a wise way we sort all the 'running' apps and 
> try to fulfill them, especially on a large-scale cluster which has heavy 
> scheduling load. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to