[
https://issues.apache.org/jira/browse/MAPREDUCE-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259647#comment-13259647
]
Andrew Hancock commented on MAPREDUCE-3267:
-------------------------------------------
I am experiencing this bug in version 0.22 as well.
It happens any time I turn on the following config in my job:
config.setFloat("mapreduce.reduce.input.buffer.percent", 0.1f);
If I remove this setting, the bug goes away.
When this option is turned on, the following symptoms are exhibited:
1. During the reduce phase many of the reduce tasks will quickly read > 100%.
The Job will then report 100% complete.
2. I have on occasion seen it then go back below 100% on the overall progress.
It will oscillate between different numbers in that case.
3. The job appears to complete normally in spite of the progress reporting
issues.
> 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
