[
https://issues.apache.org/jira/browse/MAPREDUCE-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated MAPREDUCE-3059:
-----------------------------------------------
Description:
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.
was:
Resourcemanager metrices does not have any aggregate containers allocate and
container released metrics.
If I want of how container allocated or container released, I do not know any
way to find.
NodeManager do have containers alunched and container released metrics, but
this is not central location, so get aggregate number, 1st all NM metrics
needed to be merged
Priority: Blocker (was: Major)
Affects Version/s: 0.23.0
Fix Version/s: 0.23.0
Summary: QueueMetrics do not have metrics for aggregate
containers-allocated and aggregate containers-released (was: Resourcemanager
metrices does not have aggregate containers allocated and containers released
Metrics)
> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
