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

Sourabh Goyal commented on YARN-4761:
-------------------------------------

[~sjlee0] [~zxu]]: There is still one 
[occurrence|https://github.com/apache/hadoop/blob/10468529a9b858bd945e7ecb063c9c1438efa474/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#L1008]
 of RMNode.getTotalCapability() in FSAppAttempt.java in trunk. Is this 
intentional? 

> NMs reconnecting with changed capabilities can lead to wrong cluster resource 
> calculations on fair scheduler
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4761
>                 URL: https://issues.apache.org/jira/browse/YARN-4761
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.6.4
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>            Priority: Major
>             Fix For: 2.8.0, 2.7.3, 2.6.5, 3.0.0-alpha1
>
>         Attachments: YARN-4761.01.patch, YARN-4761.02.patch
>
>
> YARN-3802 uncovered an issue with the scheduler where the resource 
> calculation can be incorrect due to async event handling. It was subsequently 
> fixed by YARN-4344, but it was never fixed for the fair scheduler.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to