hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5733) Add map/reduce slot capacity and lost map/reduce slot capacity to JobTracker metrics
Date Mon, 04 May 2009 22:52:30 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705808#action_12705808

Chris Douglas commented on HADOOP-5733:

bq. 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.

Sorry, I forgot to acknowledge this. Thanks for the explanation

> 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
>            Assignee: Sreekanth Ramakrishnan
>             Fix For: 0.21.0
>         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.

View raw message