You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Sreekanth Ramakrishnan (JIRA)" <ji...@apache.org> on 2009/05/04 08:53:31 UTC
[jira] Updated: (HADOOP-5733) Add map/reduce slot capacity and lost
map/reduce slot capacity to JobTracker metrics
[ 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-2.patch
Attaching patch incorporating the comment:
* Changed map slot and reduce slot metric from {{incrMetric}} to {{setMetric}}
* Changed the field holding, map slots and reduce slots to volatile, so the setters need not be synchronized.
* The maps and reduce slot is set in {{updateTaskTrackerStatus}} in {{JobTracker}}
* The setters for black listed slots have been made synchronized.
> 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.