[
https://issues.apache.org/jira/browse/YARN-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846951#comment-13846951
]
Sandy Ryza commented on YARN-1415:
----------------------------------
Currently, all the schedulers interpret available MB to mean non-allocated
memory. Check out CSQueueUtils.updateQueueStatistics,
FairScheduler.updateRootQueueMetrics, and FifoScheduler.nodeUpdate. If
TestQueueMetrics does not reflect this, it's TestQueueMetrics that is
misinterpreting.
> In scheduler UI, including used memory in "Memory Total" seems to be
> inaccurate
> -------------------------------------------------------------------------------
>
> Key: YARN-1415
> URL: https://issues.apache.org/jira/browse/YARN-1415
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager, scheduler
> Reporter: Siqi Li
> Fix For: 2.1.0-beta
>
> Attachments: 1.png, 2.png
>
>
> "Memory Total" is currently a sum of availableMB, allocatedMB, and
> reservedMB.
> It seems that the term "availableMB" actually means "total memory", since it
> doesn't get decreased when some jobs use a certain amount of memory.
> Hence, the Memory Total should not include allocatedMB, or availableMB
> doesn't get updated properly.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
