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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/05/06 05:28:04 UTC
[jira] [Updated] (MAPREDUCE-4710) Add peak memory usage counter for
each task
[ https://issues.apache.org/jira/browse/MAPREDUCE-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated MAPREDUCE-4710:
----------------------------------------
Labels: BB2015-05-TBR patch (was: patch)
> Add peak memory usage counter for each task
> -------------------------------------------
>
> Key: MAPREDUCE-4710
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4710
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: task
> Affects Versions: 1.0.2
> Reporter: Cindy Li
> Assignee: Cindy Li
> Priority: Minor
> Labels: BB2015-05-TBR, patch
> Attachments: MAPREDUCE-4710-trunk.patch, mapreduce-4710-v1.0.2.patch, mapreduce-4710.patch, mapreduce4710-v3.patch, mapreduce4710-v6.patch, mapreduce4710.patch
>
>
> Each task has counters PHYSICAL_MEMORY_BYTES and VIRTUAL_MEMORY_BYTES, which are snapshots of memory usage of that task. They are not sufficient for users to understand peak memory usage by that task, e.g. in order to diagnose task failures, tune job parameters or change application design. This new feature will add two more counters for each task: PHYSICAL_MEMORY_BYTES_MAX and VIRTUAL_MEMORY_BYTES_MAX.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)