[
https://issues.apache.org/jira/browse/HADOOP-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreekanth Ramakrishnan updated HADOOP-5733:
-------------------------------------------
Attachment: hadoop-5733-3.patch
*Not resetting the metrics field during {{doUpdates}}
* Setting of the slots from add/removeHostCapacity have been removed because,
in previous patches case, the map and reduce slots were incremental fields so,
when ever the capacities were added/removed it was adjusted. Now, since it is
static it is set whenever the TT statuses have updated the JT's internal
capacity fields. But it is retained when tracker is marked blacklisted we
increment/decrement in add/removeHostCapacity.
> 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
>
>
> 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.
