You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Tsuyoshi OZAWA (JIRA)" <ji...@apache.org> on 2013/01/04 09:18:14 UTC
[jira] [Updated] (MAPREDUCE-4865) Launching node-level combiner at
the end stage of MapTask and ignoring aggregated inputs at ReduceTask
[ https://issues.apache.org/jira/browse/MAPREDUCE-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsuyoshi OZAWA updated MAPREDUCE-4865:
--------------------------------------
Summary: Launching node-level combiner at the end stage of MapTask and ignoring aggregated inputs at ReduceTask (was: Launching node-level combiner at the end stage of MapTask)
> Launching node-level combiner at the end stage of MapTask and ignoring aggregated inputs at ReduceTask
> ------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-4865
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4865
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: tasktracker
> Affects Versions: 3.0.0
> Reporter: Tsuyoshi OZAWA
> Assignee: Tsuyoshi OZAWA
> Attachments: 0004-Changed-Mappers-and-Reducers-to-support-Node-level-a.patch
>
>
> MapTask needs to start node-level aggregation against local outputs at the end stage of MapTask after calling getAggregationTargets().
> This feature is implemented with Merger and CombinerRunner.
--
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