[
https://issues.apache.org/jira/browse/YARN-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116274#comment-17116274
]
Jonathan Hung commented on YARN-6492:
-------------------------------------
Ok, I see. On line 2542, can we remove the nm1 heartbeats and change the
asserts accordingly? This appears to test that requesting default partition
containers will get allocated to nm2, but if we heartbeat to nm1 before nm2,
then they will get allocated to nm1 and we lose this test case.
Can we fix the two whitespace issues too?
For TestCapacitySchedulerAutoQueueCreation test failures, it seems to be
specific to PartitionQueueMetrics/PartitionMetrics somehow. I ran these tests
before the patch and it succeeds, meaning metrics system is getting reset
properly.
Also, once we resolve these issues, will you upload patches for branches up to
branch-2.10?
> 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-junits.patch, 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,
> YARN-6492.009.WIP.patch, YARN-6492.010.WIP.patch, YARN-6492.011.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]
