[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[ https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13575156#comment-13575156 ] Hudson commented on MAPREDUCE-4893: --- Integrated in Hadoop-Hdfs-0.23-Build #520 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/520/]) MAPREDUCE-4893. MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality. Contributed by Bikas Saha (Revision 1444276) Result = SUCCESS jlowe : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1444276 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java > MR AppMaster can do sub-optimal assignment of containers to map tasks leading > to poor node locality > --- > > Key: MAPREDUCE-4893 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.0.3-alpha, 0.23.7 > > Attachments: MAPREDUCE-4893.1.patch, MAPREDUCE-4893.2.patch, > MAPREDUCE-4893.3.patch > > > Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3. > There are 10 node n1-n10 in the same rack. The RM can give it allocated > containers in the list order n5, n2, n1. The way AM map->container assignment > happens, the AM will try to assign node local maps to n5, failing which it > will assign rack local maps to n5. These rack local maps could be node local > on n2 and n1 and would have been assigned to containers on n1 and n2 if the > AM had not made an early rack local match for them on n5. This can lead to > poor locality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[ https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567652#comment-13567652 ] Hudson commented on MAPREDUCE-4893: --- Integrated in Hadoop-Mapreduce-trunk #1330 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1330/]) MAPREDUCE-4893. Fixed MR ApplicationMaster to do optimal assignment of containers to get maximum locality. Contributed by Bikas Saha. (Revision 1440749) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1440749 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java > MR AppMaster can do sub-optimal assignment of containers to map tasks leading > to poor node locality > --- > > Key: MAPREDUCE-4893 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.0.3-alpha > > Attachments: MAPREDUCE-4893.1.patch, MAPREDUCE-4893.2.patch, > MAPREDUCE-4893.3.patch > > > Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3. > There are 10 node n1-n10 in the same rack. The RM can give it allocated > containers in the list order n5, n2, n1. The way AM map->container assignment > happens, the AM will try to assign node local maps to n5, failing which it > will assign rack local maps to n5. These rack local maps could be node local > on n2 and n1 and would have been assigned to containers on n1 and n2 if the > AM had not made an early rack local match for them on n5. This can lead to > poor locality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[ https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567603#comment-13567603 ] Hudson commented on MAPREDUCE-4893: --- Integrated in Hadoop-Hdfs-trunk #1302 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1302/]) MAPREDUCE-4893. Fixed MR ApplicationMaster to do optimal assignment of containers to get maximum locality. Contributed by Bikas Saha. (Revision 1440749) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1440749 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java > MR AppMaster can do sub-optimal assignment of containers to map tasks leading > to poor node locality > --- > > Key: MAPREDUCE-4893 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.0.3-alpha > > Attachments: MAPREDUCE-4893.1.patch, MAPREDUCE-4893.2.patch, > MAPREDUCE-4893.3.patch > > > Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3. > There are 10 node n1-n10 in the same rack. The RM can give it allocated > containers in the list order n5, n2, n1. The way AM map->container assignment > happens, the AM will try to assign node local maps to n5, failing which it > will assign rack local maps to n5. These rack local maps could be node local > on n2 and n1 and would have been assigned to containers on n1 and n2 if the > AM had not made an early rack local match for them on n5. This can lead to > poor locality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[ https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567529#comment-13567529 ] Hudson commented on MAPREDUCE-4893: --- Integrated in Hadoop-Yarn-trunk #113 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/113/]) MAPREDUCE-4893. Fixed MR ApplicationMaster to do optimal assignment of containers to get maximum locality. Contributed by Bikas Saha. (Revision 1440749) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1440749 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java > MR AppMaster can do sub-optimal assignment of containers to map tasks leading > to poor node locality > --- > > Key: MAPREDUCE-4893 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.0.3-alpha > > Attachments: MAPREDUCE-4893.1.patch, MAPREDUCE-4893.2.patch, > MAPREDUCE-4893.3.patch > > > Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3. > There are 10 node n1-n10 in the same rack. The RM can give it allocated > containers in the list order n5, n2, n1. The way AM map->container assignment > happens, the AM will try to assign node local maps to n5, failing which it > will assign rack local maps to n5. These rack local maps could be node local > on n2 and n1 and would have been assigned to containers on n1 and n2 if the > AM had not made an early rack local match for them on n5. This can lead to > poor locality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[ https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567157#comment-13567157 ] Hudson commented on MAPREDUCE-4893: --- Integrated in Hadoop-trunk-Commit #3301 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3301/]) MAPREDUCE-4893. Fixed MR ApplicationMaster to do optimal assignment of containers to get maximum locality. Contributed by Bikas Saha. (Revision 1440749) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1440749 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/rm/RMContainerAllocator.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestRMContainerAllocator.java > MR AppMaster can do sub-optimal assignment of containers to map tasks leading > to poor node locality > --- > > Key: MAPREDUCE-4893 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: applicationmaster >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 2.0.3-alpha > > Attachments: MAPREDUCE-4893.1.patch, MAPREDUCE-4893.2.patch, > MAPREDUCE-4893.3.patch > > > Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3. > There are 10 node n1-n10 in the same rack. The RM can give it allocated > containers in the list order n5, n2, n1. The way AM map->container assignment > happens, the AM will try to assign node local maps to n5, failing which it > will assign rack local maps to n5. These rack local maps could be node local > on n2 and n1 and would have been assigned to containers on n1 and n2 if the > AM had not made an early rack local match for them on n5. This can lead to > poor locality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[
https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566160#comment-13566160
]
Hadoop QA commented on MAPREDUCE-4893:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12567104/MAPREDUCE-4893.3.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: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:eclipse.
{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 increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3292//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3292//console
This message is automatically generated.
> MR AppMaster can do sub-optimal assignment of containers to map tasks leading
> to poor node locality
> ---
>
> Key: MAPREDUCE-4893
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 3.0.0
>
> Attachments: MAPREDUCE-4893.1.patch, MAPREDUCE-4893.2.patch,
> MAPREDUCE-4893.3.patch
>
>
> Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3.
> There are 10 node n1-n10 in the same rack. The RM can give it allocated
> containers in the list order n5, n2, n1. The way AM map->container assignment
> happens, the AM will try to assign node local maps to n5, failing which it
> will assign rack local maps to n5. These rack local maps could be node local
> on n2 and n1 and would have been assigned to containers on n1 and n2 if the
> AM had not made an early rack local match for them on n5. This can lead to
> poor locality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[ https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551499#comment-13551499 ] Jason Lowe commented on MAPREDUCE-4893: --- The test failure appears to be unrelated, as it's failing in testUberDecision. See MAPREDUCE-4936. > MR AppMaster can do sub-optimal assignment of containers to map tasks leading > to poor node locality > --- > > Key: MAPREDUCE-4893 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 3.0.0 > > Attachments: MAPREDUCE-4893.1.patch, MAPREDUCE-4893.2.patch > > > Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3. > There are 10 node n1-n10 in the same rack. The RM can give it allocated > containers in the list order n5, n2, n1. The way AM map->container assignment > happens, the AM will try to assign node local maps to n5, failing which it > will assign rack local maps to n5. These rack local maps could be node local > on n2 and n1 and would have been assigned to containers on n1 and n2 if the > AM had not made an early rack local match for them on n5. This can lead to > poor locality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[
https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551471#comment-13551471
]
Hadoop QA commented on MAPREDUCE-4893:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12564478/MAPREDUCE-4893.2.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: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:eclipse.
{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 increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app:
org.apache.hadoop.mapreduce.v2.app.job.impl.TestJobImpl
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3232//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3232//console
This message is automatically generated.
> MR AppMaster can do sub-optimal assignment of containers to map tasks leading
> to poor node locality
> ---
>
> Key: MAPREDUCE-4893
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 3.0.0
>
> Attachments: MAPREDUCE-4893.1.patch, MAPREDUCE-4893.2.patch
>
>
> Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3.
> There are 10 node n1-n10 in the same rack. The RM can give it allocated
> containers in the list order n5, n2, n1. The way AM map->container assignment
> happens, the AM will try to assign node local maps to n5, failing which it
> will assign rack local maps to n5. These rack local maps could be node local
> on n2 and n1 and would have been assigned to containers on n1 and n2 if the
> AM had not made an early rack local match for them on n5. This can lead to
> poor locality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[
https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536617#comment-13536617
]
Hadoop QA commented on MAPREDUCE-4893:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12561811/MAPREDUCE-4893.1.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: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:eclipse.
{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 increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3145//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3145//console
This message is automatically generated.
> MR AppMaster can do sub-optimal assignment of containers to map tasks leading
> to poor node locality
> ---
>
> Key: MAPREDUCE-4893
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 3.0.0
>
> Attachments: MAPREDUCE-4893.1.patch
>
>
> Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3.
> There are 10 node n1-n10 in the same rack. The RM can give it allocated
> containers in the list order n5, n2, n1. The way AM map->container assignment
> happens, the AM will try to assign node local maps to n5, failing which it
> will assign rack local maps to n5. These rack local maps could be node local
> on n2 and n1 and would have been assigned to containers on n1 and n2 if the
> AM had not made an early rack local match for them on n5. This can lead to
> poor locality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[ https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536590#comment-13536590 ] Bikas Saha commented on MAPREDUCE-4893: --- Test passes when run locally. Trying again. > MR AppMaster can do sub-optimal assignment of containers to map tasks leading > to poor node locality > --- > > Key: MAPREDUCE-4893 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893 > Project: Hadoop Map/Reduce > Issue Type: Bug >Reporter: Bikas Saha >Assignee: Bikas Saha > Fix For: 3.0.0 > > Attachments: MAPREDUCE-4893.1.patch > > > Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3. > There are 10 node n1-n10 in the same rack. The RM can give it allocated > containers in the list order n5, n2, n1. The way AM map->container assignment > happens, the AM will try to assign node local maps to n5, failing which it > will assign rack local maps to n5. These rack local maps could be node local > on n2 and n1 and would have been assigned to containers on n1 and n2 if the > AM had not made an early rack local match for them on n5. This can lead to > poor locality. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4893) MR AppMaster can do sub-optimal assignment of containers to map tasks leading to poor node locality
[
https://issues.apache.org/jira/browse/MAPREDUCE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536564#comment-13536564
]
Hadoop QA commented on MAPREDUCE-4893:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12561803/MAPREDUCE-4893.1.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: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:eclipse.
{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 increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app:
org.apache.hadoop.mapreduce.v2.app.TestRecovery
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3143//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3143//console
This message is automatically generated.
> MR AppMaster can do sub-optimal assignment of containers to map tasks leading
> to poor node locality
> ---
>
> Key: MAPREDUCE-4893
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4893
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Bikas Saha
>Assignee: Bikas Saha
> Fix For: 3.0.0
>
> Attachments: MAPREDUCE-4893.1.patch
>
>
> Say the MR AppMaster asks the RM for 3 containers on nodes n1, n2 and n3.
> There are 10 node n1-n10 in the same rack. The RM can give it allocated
> containers in the list order n5, n2, n1. The way AM map->container assignment
> happens, the AM will try to assign node local maps to n5, failing which it
> will assign rack local maps to n5. These rack local maps could be node local
> on n2 and n1 and would have been assigned to containers on n1 and n2 if the
> AM had not made an early rack local match for them on n5. This can lead to
> poor locality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
