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/02 17:09:48 UTC
[jira] [Updated] (MAPREDUCE-2104) Rumen TraceBuilder Does Not Emit
CPU/Memory Usage Details in Traces
[ https://issues.apache.org/jira/browse/MAPREDUCE-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amar Kamat updated MAPREDUCE-2104:
----------------------------------
Attachment: mapreduce-2104-v1.7.patch
Attaching a new patch. test-patch and ant-tests passed on my box. This patch extracts resource usage metric values (like cpu-usage, physical memory, virtual memory and heap usage) into a separate class and provides setters/getters to access it.
> Rumen TraceBuilder Does Not Emit CPU/Memory Usage Details in Traces
> -------------------------------------------------------------------
>
> Key: MAPREDUCE-2104
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2104
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tools/rumen
> Affects Versions: 0.22.0
> Reporter: Ranjit Mathew
> Assignee: Amar Kamat
> Attachments: mapreduce-2104-v1.1.patch, mapreduce-2104-v1.7.patch
>
>
> Via MAPREDUCE-220, we now have CPU/Memory usage information in MapReduce JobHistory files. However, Rumen's TraceBuilder
> does not emit this information in the JSON traces. Without this information, GridMix3 cannot emulate CPU/Memory usage correctly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira