Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 23 Sep 2014 14:10:39 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12725477.1404476166000.103393.1411481439777@Atlassian.JIRA>
In-Reply-To: <JIRA.12725477.1404476166000@Atlassian.JIRA>
References: <JIRA.12725477.1404476166000@Atlassian.JIRA>
 <JIRA.12725477.1404476166708@arcas>
Subject: [jira] [Commented] (YARN-2252) Intermittent failure of
 TestFairScheduler.testContinuousScheduling
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on YARN-2252:
------------------------------

SUCCESS: Integrated in Hadoop-Hdfs-trunk #1880 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1880/])
YARN-2252. Intermittent failure of TestFairScheduler.testContinuousScheduling. (Ratandeep Ratti and kasha via kasha) (kasha: rev f5578207d2d20aa71adf12aa9f6c37b00ee9b8dc)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java
* hadoop-yarn-project/CHANGES.txt


> 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
(v6.3.4#6332)