Tsuyoshi OZAWA commented on YARN-2252:

Hi, this test failure is found on trunk - you can find it 
 Log is as follows:

Tests run: 79, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.698 sec <<< 
FAILURE! - in 
  Time elapsed: 0.582 sec  <<< FAILURE!
java.lang.AssertionError: expected:<2> but was:<1>
        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)

Can I reopen this problem?

> Intermittent failure of TestFairScheduler.testContinuousScheduling
> ------------------------------------------------------------------
>                 Key: YARN-2252
>                 URL: https://issues.apache.org/jira/browse/YARN-2252
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: trunk-win
>            Reporter: Ratandeep Ratti
>              Labels: hadoop2, scheduler, yarn
>             Fix For: 2.6.0
>         Attachments: YARN-2252-1.patch, yarn-2252-2.patch
> This test-case is failing sporadically on my machine. I think I have a 
> plausible explanation  for this.
> It seems that when the Scheduler is being asked for resources, the resource 
> requests that are being constructed have no preference for the hosts (nodes).
> The two mock hosts constructed, both have a memory of 8192 mb.
> The containers(resources) being requested each require a memory of 1024mb, 
> hence a single node can execute both the resource requests for the 
> application.
> In the end of the test-case it is being asserted that the containers 
> (resource requests) be executed on different nodes, but since we haven't 
> specified any preferences for nodes when requesting the resources, the 
> scheduler (at times) executes both the containers (requests) on the same node.

This message was sent by Atlassian JIRA

Reply via email to