[
https://issues.apache.org/jira/browse/HADOOP-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-5733:
----------------------------------
Attachment: hadoop-5733-4.patch
Merged with trunk, as conflicts with HADOOP-5738. Also re-added the blacklist
metric resets {{to doUpdates}}, since {{incrMetric}} semantics still require it
there.
{noformat}
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
{noformat}
> 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,
> hadoop-5733-3.patch, hadoop-5733-4.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.
