Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1609191597.1258517439992.JavaMail.jira@brutus>
Date: Wed, 18 Nov 2009 04:10:39 +0000 (UTC)
From: "Hong Tang (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-220) Collecting cpu and memory usage
 for MapReduce tasks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hong Tang commented on MAPREDUCE-220:
-------------------------------------

+1 on holding off this Jira until MAPREDUCE-901 is committed.

+1 on moving B* to MAPREDUCE-1218.

I'd also propose A4. Total number of child processes in the process tree rooted from the main task process. (Assuming A1, A2, A3 are cumulative metrics on all sub-processes launched by the main task process).

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