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

Ratandeep Ratti commented on YARN-2252:
---------------------------------------

Thanks for the help Wei. I think I might have found the reason for this 
failure.  Notice that the test-case 
TestFairScheduler.testLoadConfigurationOnInitialize() first starts up the 
continuousScheduling thread (under FairScheduler object). When the execution 
flow reaches the test-case TestFairScheduler.testContinuousScheduling, even 
though we create a new FairScheduler object, the old thread 
(continuousScheduling) is still live, and now, there are now two live 
continuousScheduling threads trying to assign containers to nodes. 

The problem does not seem to occur when I properly stop each thread before 
starting another execution of this test-case.

> Intermittent failure for testcase 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
>
> 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
(v6.2#6252)

Reply via email to