[jira] [Commented] (MAPREDUCE-5008) Merger progress miscounts with respect to EOF_MARKER

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580025#comment-13580025 ] 

Hadoop QA commented on MAPREDUCE-5008:
--------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12569684/MAPREDUCE-5008-branch-1.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3337//console

This message is automatically generated.
                
> 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
>         Attachments: MAPREDUCE-5008-branch-1.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