hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-220) Collecting cpu and memory usage for MapReduce tasks
Date Tue, 17 Nov 2009 20:32:39 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779109#action_12779109
] 

dhruba borthakur commented on MAPREDUCE-220:
--------------------------------------------

Are we proposing that we add the following metrics to the heartbeat message?

A1. virtual memory used by each task (in bytes)
A2. physical memory  used by each task (in bytes)
A3. cpu used by each task (as a percentage of total CPU on that machine)

B1. available physical memory on this machine (in bytes)
B2. available cpu on this machine (as a percentage of total CPU on that machine)

> 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
>
> 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