[
https://issues.apache.org/jira/browse/YARN-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201432#comment-16201432
]
Manikandan R commented on YARN-6492:
------------------------------------
Sorry for the delay. Had a offline discussions with [~Naganarasimha] &
[~sunilg] regarding the structure and POC patch to deliver the same. It has
taken a shape and attached JMX o/p for further discussions. Attached o/p has 1.
PartitionQueueMetrics and 2. QueueMetrics.
1. For POC, We had two partitions, x & y. Hence o/p will have
PartitionQueueMetrics for both the partitions. Under each
PartitionQueueMetrics, QueueMetrics for each queue and UserMetrics for each
user would be available.
2. We have retained existing QueueMetrics for backward compatiblity which also
has been captured in o/p for better understanding.
[~jlowe] [~jhung] [~sunilg] Thoughts?
> Generate queue metrics for each partition
> -----------------------------------------
>
> Key: YARN-6492
> URL: https://issues.apache.org/jira/browse/YARN-6492
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler
> Reporter: Jonathan Hung
> Assignee: Manikandan R
> Attachments: YARN-6492.001.patch, partition_metrics.txt
>
>
> We are interested in having queue metrics for all partitions. Right now each
> queue has one QueueMetrics object which captures metrics either in default
> partition or across all partitions. (After YARN-6467 it will be in default
> partition)
> But having the partition metrics would be very useful.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
