[
https://issues.apache.org/jira/browse/MAPREDUCE-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza updated MAPREDUCE-5008:
----------------------------------
Description:
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.
was:
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.
> 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
>
> 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
