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 "Amar Kamat (JIRA)" <ji...@apache.org> on 2011/06/01 08:35:47 UTC
[jira] [Updated] (MAPREDUCE-2469) Task counters should also report
the total heap usage of the task
[ https://issues.apache.org/jira/browse/MAPREDUCE-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated MAPREDUCE-2469:
----------------------------------
Attachment: mapreduce-2469-v1.3.patch
Attaching a new patch that makes the testcase's memory loader static so that once the map class gets loaded, the loader stays in the jvm's heap without getting GCed.
> Task counters should also report the total heap usage of the task
> -----------------------------------------------------------------
>
> Key: MAPREDUCE-2469
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2469
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
> Affects Versions: 0.23.0
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Labels: mapreduce
> Attachments: 2469.v0.1.patch, mapreduce-2469-v1.1.patch, mapreduce-2469-v1.2.patch, mapreduce-2469-v1.3.patch
>
>
> Currently, the task counters report VSS and RSS usage of the task. The task counter should also report the total heap usage of the task also. The task might be configured with a max heap size of M but the task's total heap usage might only be H, where H < M. In such a case, knowing only M doesn't provide a complete picture of the task's memory usage.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira