You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Sandy Ryza (JIRA)" <ji...@apache.org> on 2013/07/29 07:27:50 UTC
[jira] [Commented] (MAPREDUCE-5059) Job overview shows average
merge time larger than for any reduce attempt
[ https://issues.apache.org/jira/browse/MAPREDUCE-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722162#comment-13722162 ]
Sandy Ryza commented on MAPREDUCE-5059:
---------------------------------------
This appears to be in branch-2, but not trunk
> Job overview shows average merge time larger than for any reduce attempt
> ------------------------------------------------------------------------
>
> Key: MAPREDUCE-5059
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5059
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobhistoryserver, webapps
> Reporter: Jason Lowe
> Assignee: Omkar Vinit Joshi
> Fix For: 2.1.0-beta, 0.23.8
>
> Attachments: MAPREDUCE-5059-20130325.patch, MAPREDUCE-5059-20130410.patch
>
>
> When looking at a job overview page on the history server, the Average Merge Time is often reported with a value that is far larger than the Elapsed Merge Time shown for any reduce task attempt. The job overview page calculates the merge time as the time delta between the sort finishing and the job launching while the attempts page calculates it as the time delta between the sort finishing and the shuffle finishing.
--
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