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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2016/01/13 23:42:40 UTC
[jira] [Updated] (MAPREDUCE-5883) "Total megabyte-seconds" in job
counters is slightly misleading
[ https://issues.apache.org/jira/browse/MAPREDUCE-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kumar Vavilapalli updated MAPREDUCE-5883:
-----------------------------------------------
Fix Version/s: (was: 2.7.3)
2.7.2
Pulled this into 2.7.2 to keep the release up-to-date with 2.6.3. Changing fix-versions to reflect the same.
> "Total megabyte-seconds" in job counters is slightly misleading
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-5883
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5883
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Nathan Roberts
> Assignee: Nathan Roberts
> Priority: Minor
> Labels: BB2015-05-TBR
> Fix For: 2.7.2, 2.6.3
>
> Attachments: MAPREDUCE-5883.patch
>
>
> The following counters are in milliseconds so "megabyte-seconds" might be better stated as "megabyte-milliseconds"
> MB_MILLIS_MAPS.name= Total megabyte-seconds taken by all map tasks
> MB_MILLIS_REDUCES.name= Total megabyte-seconds taken by all reduce tasks
> VCORES_MILLIS_MAPS.name= Total vcore-seconds taken by all map tasks
> VCORES_MILLIS_REDUCES.name= Total vcore-seconds taken by all reduce tasks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)