hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1440) JobClient should not sort input-splits
Date Thu, 11 Feb 2010 18:04:54 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832605#action_12832605

Owen O'Malley commented on HADOOP-1440:

This was reverted because of a fatal bug that it caused. I must have forgotten to reopen the
jira. *frown* Sorry about that. I've opened a new jira MAPREDUCE-1484.

> JobClient should not sort input-splits
> --------------------------------------
>                 Key: HADOOP-1440
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1440
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 0.12.3
>         Environment: All
>            Reporter: Milind Bhandarkar
>            Assignee: Senthil Subramanian
>             Fix For: 0.14.0
>         Attachments: HADOOP-1440_1.patch
> Currently, the JobClient sorts the InputSplits returned by InputFormat in descending
order, so that the map tasks corresponding to larger input-splits are scheduled first for
execution than smaller ones. However, this causes problems in applications that produce data-sets
partitioned similarly to the input partition with -reducer NONE.
> With -reducer NONE, map task i produces part-i. Howver, in the typical applications that
use -reducer NONE it should produce a partition that has the same index as the input parrtition.
> (Of course, this requires that each partition should be fed in its entirety to a map,
rather than splitting it into blocks, but that is a separate issue.)
> Thus, sorting input splits should be either controllable via a configuration variable,
or the FileInputFormat should sort the splits and JobClient should honor the order of splits.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message