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 "Akira AJISAKA (JIRA)" <ji...@apache.org> on 2015/05/08 13:23:00 UTC

[jira] [Commented] (YARN-3432) Cluster metrics have wrong Total Memory when there is reserved memory on CS

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

Akira AJISAKA commented on YARN-3432:
-------------------------------------

I'm thinking changing how to calculate total memory when the scheduler is CapacityScheduler is straightforward.
{code}
  if (rs instanceof CapacityScheduler) {
    this.totalMB = availableMB + allocatedMB + reservedMB;
  } else {
    this.totalMB = availableMB + allocatedMB;
  }
{code}
Hi [~tgraves] and [~brahmareddy], what do you think?

> 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
>
> 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)