[jira] [Updated] (MAPREDUCE-3059) QueueMetrics do not have metrics for aggregate containers-allocated and aggregate containers-released

["Devaraj K (Updated) (JIRA)" <ji...@apache.org>]

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

Devaraj K updated MAPREDUCE-3059:
---------------------------------

    Attachment: MAPREDUCE-3059.patch
    
> QueueMetrics do not have metrics for aggregate containers-allocated and aggregate containers-released
> -----------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3059
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3059
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Karam Singh
>            Assignee: Devaraj K
>            Priority: Blocker
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-3059.patch
>
>
> QueueMetrics for ResourceManager do not have any metrics for aggregate containers-allocated and containers-released.
> We need the aggregates of containers-allocated and containers-released to figure out the rate at which RM is dishing out containers. NodeManager do have containers-launched and container-released metrics, but this is not across all nodes; so to get the cluster level aggregate, we need to preprocess NM metrics from all nodes - which is troublesome.
> Currently, we do have AllocatedContainers and PendingContainers which reflect the running containers given out to AMs, and containers waiting for allocation respectively.

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