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 "Evan Wang (JIRA)" <ji...@apache.org> on 2010/07/12 13:44:58 UTC
[jira] Commented: (MAPREDUCE-220) Collecting cpu and memory usage
for MapReduce tasks
[ https://issues.apache.org/jira/browse/MAPREDUCE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887349#action_12887349 ]
Evan Wang commented on MAPREDUCE-220:
-------------------------------------
why not collect disk i/o and bandwidth for scheduling as well?
> 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
> Components: task, tasktracker
> Reporter: Hong Tang
> Assignee: Scott Chen
> Fix For: 0.22.0
>
> Attachments: MAPREDUCE-220-20100616.txt, MAPREDUCE-220-v1.txt, 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.