You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2013/07/31 06:27:48 UTC

[jira] [Resolved] (MAPREDUCE-5437) MR2 specific metrics should be collected

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Srimanth Gunturi resolved MAPREDUCE-5437.
-----------------------------------------

    Resolution: Won't Fix

MR2 applications are too split up to have a central place where their metrics can be gathered. Job history server cannot give real time MR2 metrics. Since this is long term work, this particular issue is being resolved.  
                
> MR2 specific metrics should be collected
> ----------------------------------------
>
>                 Key: MAPREDUCE-5437
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5437
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.1.0-beta
>            Reporter: Srimanth Gunturi
>
> We have a usecase to show the below information. We can find job count by calling the /apps endpoint and filtering by type/state. But we need a way (JMX/API) to get the number of map/red tasks that are running/waiting.
> {noformat}
> Total Jobs: x jobs
> Tasks: Maps	a running / b waiting
> Tasks: Reduces	c running / d waiting
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira