[MAPREDUCE-2104] Rumen TraceBuilder Does Not Emit CPU/Memory Usage Details in Traces

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.22.0
• Fix Version/s: 0.23.0
• Component/s: tools/rumen
• Hadoop Flags: Reviewed
• Release Note: Adds cpu, physical memory, virtual memory and heap usages to TraceBuilder's output.
• Tags: rumen resource-usage
• Assignee: Amar Kamat
• Reporter: Ranjit Mathew
• Created: 04/Oct/10 11:04
• Updated: 02/May/13 02:29
• Resolved: 06/Jun/11 05:42

Description

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.

Issue Links

• blocks: MAPREDUCE-1702 CPU/Memory emulation for GridMix3
• depends upon: MAPREDUCE-220 Collecting cpu and memory usage for MapReduce tasks
• is superceded by: MAPREDUCE-2469 Task counters should also report the total heap usage of the task