[
https://issues.apache.org/jira/browse/MAPREDUCE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859454#action_12859454
]
dhruba borthakur commented on MAPREDUCE-220:
--------------------------------------------
hi folks, we would like to start work on this one. In the earlier discussion,
we said that a pre-requisite is to refactor all the metric reporting via
MAPREDUCE-901. But 901 is not moving forward. Given that fact, is it ok with
people if we start working on this JIRA using the existing reporting framework
even before M901 is done?
> 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.
