[
https://issues.apache.org/jira/browse/YARN-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901600#comment-15901600
]
Jason Lowe commented on YARN-4236:
----------------------------------
Oops spoke too soon. Just before committing I noticed there's a place that was
missed. There are two QueueMetrics#allocateResources methods, and the patch
only increments the new aggregate metrics in one of the cases. The case that
was missed is used for the scenario where an existing container is changing its
allocation size. Arguably an increase in container size probably should be
treated like an allocation of the delta for aggregate calculation purposes.
For a decrease in size, that's sort of like a release of the delta size, and
aggregate calculations ignore releases.
> Metric for aggregated resources allocation per queue
> ----------------------------------------------------
>
> Key: YARN-4236
> URL: https://issues.apache.org/jira/browse/YARN-4236
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: metrics, scheduler
> Reporter: Chang Li
> Assignee: Chang Li
> Labels: oct16-medium
> Attachments: YARN-4236.2.patch, YARN-4236-3.patch, YARN-4236.patch
>
>
> We currently track allocated memory and allocated vcores per queue but we
> don't have a good rate metric on how fast we're allocating these things. In
> other words, a straight line in allocatedmb could equally be one extreme of
> no new containers are being allocated or allocating a bunch of containers
> where we free exactly what we allocate each time. Adding a resources
> allocated per second per queue would give us a better insight into the rate
> of resource churn on a queue. Based on this aggregated resource allocation
> per queue we can easily have some tools to measure the rate of resource
> allocation per queue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
