hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Parker (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5186) mapreduce.job.max.split.locations causes some splits created by CombineFileInputFormat to fail
Date Thu, 24 Oct 2013 21:26:02 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Parker updated MAPREDUCE-5186:
-------------------------------------

    Attachment: MAPREDUCE-5186v2.patch

[~sjlee0] I originally tried to restore the mrv1 functionality, but it seems that max block
locations is an artifact from mrv1 to protect the jobtracker and it is not clear to me what
function it serves with respect to an AM.  I am modified the patch to remove m.j,max.split.locations.

> mapreduce.job.max.split.locations causes some splits created by CombineFileInputFormat
to fail
> ----------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5186
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5186
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: job submission
>    Affects Versions: 2.0.4-alpha, 2.2.0
>            Reporter: Sangjin Lee
>            Assignee: Robert Parker
>            Priority: Critical
>         Attachments: MAPREDUCE-5186v1.patch, MAPREDUCE-5186v2.patch
>
>
> CombineFileInputFormat can easily create splits that can come from many different locations
(during the last pass of creating "global" splits). However, we observe that this often runs
afoul of the mapreduce.job.max.split.locations check that's done by JobSplitWriter.
> The default value for mapreduce.job.max.split.locations is 10, and with any decent size
cluster, CombineFileInputFormat creates splits that are well above this limit.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message