[
https://issues.apache.org/jira/browse/MAPREDUCE-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125601#comment-13125601
]
Devaraj K commented on MAPREDUCE-3059:
--------------------------------------
Hi Mahadev,
I agree that we can calculate the information w.r.t. containers at RM itself.
But what i meant is not just container metrics information but any other metric
information e.g. NodeManager jvm metrics information or similar metric
information which might be of help to administrator to get an idea about what's
happening on complete cluster.
> 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
>
>
> 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
