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 "Ming Ma (JIRA)" <ji...@apache.org> on 2013/11/07 23:31:18 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13816725#comment-13816725 ] 

Ming Ma commented on MAPREDUCE-4710:
------------------------------------

It doesn’t seem to be MR application specific, other YARN application might want this as well. Should it be done at NM level so that there are general container peak memory usage data?

> 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: patch
>         Attachments: MAPREDUCE-4710-trunk.patch, mapreduce-4710-v1.0.2.patch, mapreduce-4710.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.1#6144)