hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cindy Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4710) Add peak memory usage counter for each task
Date Mon, 26 Nov 2012 21:45:02 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504133#comment-13504133
] 

Cindy Li commented on MAPREDUCE-4710:
-------------------------------------

Thanks for the comments, Harsh and Arun!

I've added the change to interface for hadoop 1.0.2 version. Similar change will be applied
to the trunk and patch for trunk will be updated soon. 
                
> 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.patch, mapreduce-4710-v1.0.2.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 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

Mime
View raw message