[
https://issues.apache.org/jira/browse/HADOOP-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705523#action_12705523
]
Chris Douglas commented on HADOOP-5733:
---------------------------------------
* When using {{setMetric}}, doUpdates shouldn't reset the metric to 0
* set\*Slots doesn't need to be adjusted in add/removeHostCapacity, as in the
original patch?
> Add map/reduce slot capacity and lost map/reduce slot capacity to JobTracker
> metrics
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-5733
> URL: https://issues.apache.org/jira/browse/HADOOP-5733
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred, metrics
> Reporter: Hong Tang
> Attachments: hadoop-5733-1.patch, hadoop-5733-2.patch
>
>
> It would be nice to have the actual map/reduce slot capacity and the lost
> map/reduce slot capacity (# of blacklisted nodes * map-slot-per-node or
> reduce-slot-per-node). This information can be used to calculate a JT view of
> slot utilization.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.