[
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
