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

Hudson commented on YARN-7414:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13239 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13239/])
YARN-7414. FairScheduler#getAppWeight() should be moved into (templedf: rev 
b246c547490dd94271806ca4caf1e5f199f0fb09)
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSAppAttempt.java
* (edit) 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java


> FairScheduler#getAppWeight() should be moved into FSAppAttempt#getWeight()
> --------------------------------------------------------------------------
>
>                 Key: YARN-7414
>                 URL: https://issues.apache.org/jira/browse/YARN-7414
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler
>    Affects Versions: 3.0.0-beta1
>            Reporter: Daniel Templeton
>            Assignee: Soumabrata Chakraborty
>            Priority: Minor
>              Labels: newbie
>             Fix For: 3.1.0, 3.0.1
>
>         Attachments: YARN-7414.001.patch, YARN-7414.002.patch, 
> YARN-7414.003.patch
>
>
> It's illogical that {{FSAppAttempt}} defers to {{FairScheduler}} for its own 
> weight, especially when {{FairScheduler}} has to call back to 
> {{FSAppAttempt}} to get the details to return a value. Instead, 
> {{FSAppAttempt}} should do the work and call out to {{FairScheduler}} to get 
> the details it needs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to