hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5223) Refactor reduce shuffle code
Date Thu, 12 Feb 2009 09:09:59 GMT

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

Arun C Murthy commented on HADOOP-5223:

Forgot to add that we felt it's better to move the responsibility of tracking the shuffle
into a new ShuffleScheduler; the Fetcher directly informs the ShuffleScheduler about the success/failure
of each map-output without going through another queue of CopyResult as-is today.

> Refactor reduce shuffle code
> ----------------------------
>                 Key: HADOOP-5223
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5223
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.21.0
>         Attachments: HADOOP-5233_api.patch, HADOOP-5233_part0.patch
> The reduce shuffle code has become very complex and entangled. I think we should move
it out of ReduceTask and into a separate package (org.apache.hadoop.mapred.task.reduce). Details
to follow.

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

View raw message