hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3443) map outputs should not be renamed between partitions
Date Sun, 25 May 2008 15:47:55 GMT

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

Owen O'Malley updated HADOOP-3443:

    Attachment: hadoop-3443-1.patch

This patch uses the same directory for the final outputs in the case that there is a single
spill. It also adds some logging so you can understand if (and why) the mapper's sort spilled.

> map outputs should not be renamed between partitions
> ----------------------------------------------------
>                 Key: HADOOP-3443
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3443
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.17.0
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>            Priority: Critical
>         Attachments: hadoop-3443-1.patch
> If a map finishes with out having to spill its data buffer, the map outputs are sorted
and written to disk. However, no care is taken to make sure that the same partition is used
to write it out before it is renamed. On nodes with multiple disks assigned to the task trackers,
this will likely cause an addition read/write cycle to disk that is very expensive.

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

View raw message