You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Tao Yang (JIRA)" <ji...@apache.org> on 2018/06/20 12:38:00 UTC
[jira] [Updated] (YARN-8443) Cluster metrics have wrong Total
VCores when there is reserved container for CapacityScheduler
[ https://issues.apache.org/jira/browse/YARN-8443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tao Yang updated YARN-8443:
---------------------------
Attachment: YARN-8443.001.patch
> Cluster metrics have wrong Total VCores when there is reserved container for CapacityScheduler
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-8443
> URL: https://issues.apache.org/jira/browse/YARN-8443
> Project: Hadoop YARN
> Issue Type: Bug
> Components: webapp
> Affects Versions: 2.9.0, 3.1.0, 3.2.0
> Reporter: Tao Yang
> Assignee: Tao Yang
> Priority: Major
> Attachments: YARN-8443.001.patch
>
>
> Cluster metrics on the web UI will give wrong Total Vcores when there is reserved container for CapacityScheduler.
> Reference code:
> {code:java|title=ClusterMetricsInfo.java}
> if (rs instanceof CapacityScheduler) {
> CapacityScheduler cs = (CapacityScheduler) rs;
> this.totalMB = availableMB + allocatedMB + reservedMB;
> this.totalVirtualCores =
> availableVirtualCores + allocatedVirtualCores + containersReserved;
> ...
> }
> {code}
> The key of this problem is the calculation of totalVirtualCores, {{containersReserved}} is the number of reserved containers, not reserved VCores. The correct calculation should be {{this.totalVirtualCores = availableVirtualCores + allocatedVirtualCores + reservedVirtualCores;}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org