[jira] [Commented] (YARN-4761) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler

[Sangjin Lee (JIRA)]

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

Sangjin Lee commented on YARN-4761:
-----------------------------------

To see this, you add this code to 
{{TestResourceTrackerService#testReconnectNode}}:
{code}
  public void testReconnectNode() throws Exception {
    Configuration conf = new Configuration();
    conf.set(YarnConfiguration.RM_SCHEDULER,
        
"org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler");
    rm = new MockRM(conf) {
    ...
{code}

and the test breaks:
{noformat}
testReconnectNode(org.apache.hadoop.yarn.server.resourcemanager.TestResourceTrackerService)
  Time elapsed: 1.188 sec  <<< FAILURE!
java.lang.AssertionError: expected:<15360> but was:<10240>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotEquals(Assert.java:743)
        at org.junit.Assert.assertEquals(Assert.java:118)
        at org.junit.Assert.assertEquals(Assert.java:555)
        at org.junit.Assert.assertEquals(Assert.java:542)
        at 
org.apache.hadoop.yarn.server.resourcemanager.TestResourceTrackerService.testReconnectNode(TestResourceTrackerService.java:1044)
{noformat}

> 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
>
> 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)