hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Chen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-220) Collecting cpu and memory usage for MapReduce tasks
Date Wed, 28 Apr 2010 20:31:59 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Scott Chen updated MAPREDUCE-220:
---------------------------------

    Attachment: MAPREDUCE-220.txt

This patch implements the feature that transmit the per task CPU and memory information through
TaskTracker heartbeat.
Here's a summary of the changes:

1. Add three methods in LinuxResourceCalculatorPlugin to get the cumulative CPU time, physical
memory and virtual memory of a process (aggregated all the subprocesses)..
2. Add a method called resourceStatusUpdate in TaskTracker to update the resource status in
TaskStatus.taskReports before sending heartbeat.
3. Add a nested class called ResourceStatus in TaskStatus to store the CPU and memory information.
3. Modify TestTTResource to check if the per task resource information actually transmitted.

> Collecting cpu and memory usage for MapReduce tasks
> ---------------------------------------------------
>
>                 Key: MAPREDUCE-220
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-220
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>            Reporter: Hong Tang
>            Assignee: Scott Chen
>         Attachments: MAPREDUCE-220.txt
>
>
> It would be nice for TaskTracker to collect cpu and memory usage for individual Map or
Reduce tasks over time.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message