[
https://issues.apache.org/jira/browse/MAPREDUCE-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588210#comment-13588210
]
Hudson commented on MAPREDUCE-5008:
-----------------------------------
Integrated in Hadoop-trunk-Commit #3389 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/3389/])
MAPREDUCE-5008. Merger progress miscounts with respect to EOF_MARKER.
Contributed by Sandy Ryza. (Revision 1450723)
Result = SUCCESS
tomwhite :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1450723
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/task/reduce/MergeManagerImpl.java
> Merger progress miscounts with respect to EOF_MARKER
> ----------------------------------------------------
>
> Key: MAPREDUCE-5008
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5008
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.0.3-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Fix For: 1.2.0, 2.0.4-beta
>
> Attachments: MAPREDUCE-5008-branch-1.patch, MAPREDUCE-5008.patch,
> MAPREDUCE-5008.patch
>
>
> After MAPREDUCE-2264, a segment's raw data length is calculated without the
> EOF_MARKER bytes. However, when the merge is counting how many bytes it
> processed, it includes the marker. This can cause the merge progress to go
> above 100%.
> Whether these EOF_MARKER bytes should count should be consistent between the
> two.
> This a JIRA instead of an amendment because MAPREDUCE-2264 already went into
> 2.0.3.
--
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
