[
https://issues.apache.org/jira/browse/YARN-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989049#comment-14989049
]
qiang xu commented on YARN-3432:
--------------------------------
I think we need to think about the vcore too.
In current code, it is:
this.totalMB = availableMB + allocatedMB;
this.totalVirtualCores = availableVirtualCores + allocatedVirtualCores;
Do we need to make this.totalVirtualCores = availableVirtualCores +
allocatedVirtualCores+containersReserved;
> Cluster metrics have wrong Total Memory when there is reserved memory on CS
> ---------------------------------------------------------------------------
>
> Key: YARN-3432
> URL: https://issues.apache.org/jira/browse/YARN-3432
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler, resourcemanager
> Affects Versions: 2.6.0
> Reporter: Thomas Graves
> Assignee: Brahma Reddy Battula
> Attachments: YARN-3432-002.patch, YARN-3432.patch
>
>
> I noticed that when reservations happen when using the Capacity Scheduler,
> the UI and web services report the wrong total memory.
> For example. I have a 300GB of total memory in my cluster. I allocate 50
> and I reserve 10. The cluster metrics for total memory get reported as 290GB.
> This was broken by https://issues.apache.org/jira/browse/YARN-656 so perhaps
> there is a difference between fair scheduler and capacity scheduler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
