[
https://issues.apache.org/jira/browse/MAPREDUCE-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated MAPREDUCE-2469:
----------------------------------
Status: Open (was: Patch Available)
TestJobCounters passed on my box. My guess is that the JVM is releasing the
memory to the OS after the GC, causing Runtime.getRuntime().totalMemory() to
decrease before it gets recorded in the task's counter. Its very much dependent
on the kernel. Some linux kernels dont support this feature (including the one
which I am using). I will debug this further.
> 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
>
>
> 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
