Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 4 Mar 2013 19:15:14 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12559127.1338789962169.376982.1362424514986@arcas>
In-Reply-To: <JIRA.12559127.1338789962169@arcas>
References: <JIRA.12559127.1338789962169@arcas>
Subject: [jira] [Commented] (YARN-18) Make locatlity in YARN's container
 assignment and task scheduling pluggable for other deployment topology
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/YARN-18?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1359251=
7#comment-13592517 ]=20

Hadoop QA commented on YARN-18:
-------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest a=
ttachment=20
  http://issues.apache.org/jira/secure/attachment/12571919/YARN-18-v3.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author=
 tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 =
new or modified test files.

  {color:red}-1 one of tests included doesn't have a timeout.{color}

    {color:green}+1 javac{color}.  The applied patch does not increase the =
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any =
warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:e=
clipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new =
Findbugs (version 1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not incre=
ase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hado=
op-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app ha=
doop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop=
-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit te=
sts.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/459//testR=
eport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/459//con=
sole

This message is automatically generated.
               =20
> Make locatlity in YARN's container assignment and task scheduling pluggab=
le for other deployment topology
> -------------------------------------------------------------------------=
--------------------------------
>
>                 Key: YARN-18
>                 URL: https://issues.apache.org/jira/browse/YARN-18
>             Project: Hadoop YARN
>          Issue Type: New Feature
>    Affects Versions: 2.0.3-alpha
>            Reporter: Junping Du
>            Assignee: Junping Du
>              Labels: features
>         Attachments: HADOOP-8474-ContainerAssignmentTaskScheduling-plugga=
ble.patch, MAPREDUCE-4309.patch, MAPREDUCE-4309-v2.patch, MAPREDUCE-4309-v3=
.patch, MAPREDUCE-4309-v4.patch, MAPREDUCE-4309-v5.patch, MAPREDUCE-4309-v6=
.patch, MAPREDUCE-4309-v7.patch, YARN-18.patch, YARN-18-v2.patch, YARN-18-v=
3.patch
>
>
> There are several classes in YARN=E2=80=99s container assignment and task=
 scheduling algorithms that relate to data locality which were updated to g=
ive preference to running a container on other locality besides node-local =
and rack-local (like nodegroup-local). This propose to make these data stru=
cture/algorithms pluggable, like: SchedulerNode, RMNodeImpl, etc. The inner=
 class ScheduledRequests was made a package level class to it would be easi=
er to create a subclass, ScheduledRequestsWithNodeGroup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira