[
https://issues.apache.org/jira/browse/YARN-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182542#comment-15182542
]
Hudson commented on YARN-4761:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9429 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9429/])
YARN-4761. NMs reconnecting with changed capabilities can lead to wrong (zxu:
rev e1ccc9622b2f1fbefea1862fa74d1fb56d8eb264)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestAbstractYarnScheduler.java
*
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
> 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
> 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
(v6.3.4#6332)
