[ 
https://issues.apache.org/jira/browse/YARN-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18089261#comment-18089261
 ] 

ASF GitHub Bot commented on YARN-11965:
---------------------------------------

zhengchenyu commented on PR #8547:
URL: https://github.com/apache/hadoop/pull/8547#issuecomment-4714141971

   @K0K0V0K 
   On a cluster of 10,000+ nodes, having one partition per node is not a 
practical use case, as it would significantly increase the operational burden. 
Generally, there are only a few NodeLabels, and each partition only has 14 
fields, so I don't think it will create a significant burden.




> Support partition-aware resource metrics in RM cluster metrics REST API
> -----------------------------------------------------------------------
>
>                 Key: YARN-11965
>                 URL: https://issues.apache.org/jira/browse/YARN-11965
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Chenyu Zheng
>            Assignee: Chenyu Zheng
>            Priority: Major
>              Labels: pull-request-available
>
> When node labels are enabled, different labels represent separate resource 
> pools. However, the RM REST API `/ws/v1/cluster/metrics` currently exposes 
> fields such as totalMB and totalVirtualCores based on the default partition 
> only. As a result, resources from non-default partitions are not visible to 
> external resource management systems, which may incorrectly determine that 
> the cluster has no available capacity after new labels are added.
> The API should expose cluster resource metrics across all partitions and 
> provide partition-level metrics so clients can distinguish capacity and usage 
> by node label.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to