[jira] [Commented] (MAPREDUCE-4435) Expose JobTracker metrics for number of reducers in shuffle vs. sort vs. reduce phase

["Arun C Murthy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413330#comment-13413330 ] 

Arun C Murthy commented on MAPREDUCE-4435:
------------------------------------------

Eirik, seems reasonable.

Could you please add a test case?

Also, a minor improvement would be to store the Map<Phase,Integer> in TaskTrackerStatus to save a recompute - not that it matters a whole lot... :)
                
> Expose JobTracker metrics for number of reducers in shuffle vs. sort vs. reduce phase
> -------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4435
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4435
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobtracker, tasktracker
>            Reporter: Eirik Bakke
>         Attachments: mapreduce.patch
>
>
> We'd like to be able to show our Cloudera Manager users some more detailed metrics about the number of reducers running at any given time--specifically, how many reducers are running in each of the three possible phases (shuffle, sort, and reduce). This would require the addition of some new overridable methods to the JobTrackerInstrumentation API, plus a little bit of code to actually call them from the JobTracker class. The necessary information seems to already be available in the TaskStatus object. The attached patch (which I've tested on hadoop-common/branch-1.0) shows one way to do it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira