[
https://issues.apache.org/jira/browse/YARN-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103520#comment-17103520
]
Jonathan Hung commented on YARN-6492:
-------------------------------------
Ok I see. This was not my original understanding. I assumed YARN-6467 was filed
standalone, then I filed this ticket because I saw YARN-6467 would remove
partitioned metrics. IMO if there's multiple JIRAs that require a feature to
work properly, they shouldn't be committed separately.
In any case, YARN-6467 has already made its way into releases, so we have
already broken compatibility. Hence, I think we should treat "original
queuemetrics computation" as behavior *after* YARN-6467 (I don't want this JIRA
to reverse the behavior from YARN-6467, thus breaking compatibility again).
[[email protected]] [~epayne] let me know if this makes sense.
> 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
> Priority: Major
> Attachments: PartitionQueueMetrics_default_partition.txt,
> PartitionQueueMetrics_x_partition.txt, PartitionQueueMetrics_y_partition.txt,
> YARN-6492.001.patch, YARN-6492.002.patch, YARN-6492.003.patch,
> YARN-6492.004.patch, YARN-6492.005.WIP.patch, YARN-6492.006.WIP.patch,
> YARN-6492.007.WIP.patch, YARN-6492.008.WIP.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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
