You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2019/03/21 11:22:00 UTC
[jira] [Resolved] (MAPREDUCE-7091) Terasort on S3A to switch to new
committers
[ https://issues.apache.org/jira/browse/MAPREDUCE-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved MAPREDUCE-7091.
---------------------------------------
Resolution: Duplicate
Fix Version/s: 3.3.0
> Terasort on S3A to switch to new committers
> -------------------------------------------
>
> Key: MAPREDUCE-7091
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7091
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: examples
> Affects Versions: 3.1.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 3.3.0
>
>
> Terasort is very slow on S3, because it still uses the classic rename-to-commit algorithm on the sort, even while teragen and the reporting can use the new committer
> Reason: {{org.apache.hadoop.examples.terasort.TeraOutputFormat}} has overriden {{getOutputCommitter}} even though it doesn't need to.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org