[
https://issues.apache.org/jira/browse/MAPREDUCE-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173576#comment-13173576
]
Todd Lipcon commented on MAPREDUCE-3267:
----------------------------------------
This was on 0.23.0 before release, so might be fixed by now. I do think I was
using intermediate compression and maybe some of the "in-memory merge" config
options. I _think_ this was the config I used for the job:
{code}
<property>
<name>io.sort.mb</name>
<value>650</value>
</property>
<property>
<name>mapreduce.map.sort.spill.percent</name>
<value>0.98</value>
</property>
<property>
<name>mapreduce.reduce.shuffle.input.buffer.percent</name>
<value>0.8</value>
</property>
<property>
<name>mapreduce.reduce.input.buffer.percent</name>
<value>0.8</value>
</property>
<property>
<name>io.sort.factor</name>
<value>100</value>
</property>
{code}
and it was a terasort
> MR2 reduce tasks showing >100% complete
> ---------------------------------------
>
> Key: MAPREDUCE-3267
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3267
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, task
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Ravi Prakash
>
> My job is currently showing >100% reduce completion. Some reduce tasks are
> much higher than 100% complete. they appear to be in the "last merge pass"
> stage
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
