[
https://issues.apache.org/jira/browse/MAPREDUCE-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695988#comment-13695988
]
Hadoop QA commented on MAPREDUCE-5352:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12590118/MAPREDUCE-5352.2.txt
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-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3813//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3813//console
This message is automatically generated.
> Optimize node local splits generated by CombineFileInputFormat
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-5352
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5352
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 2.0.5-alpha
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: MAPREDUCE-5352.1.txt, MAPREDUCE-5352.2.txt
>
>
> CombineFileInputFormat currently walks through all available nodes and
> generates multiple (maxSplitsPerNode) splits on a single node before
> attempting to generate splits on subsequent nodes. This ends up reducing the
> possibility of generating splits for subsequent nodes - since these blocks
> will no longer be available for subsequent nodes. Allowing splits to go 1
> block above the max-split-size makes this worse.
> Allocating a single split per node in one iteration, should help increase the
> distribution of splits across nodes - so the subsequent nodes will have more
> blocks to choose from.
--
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
