hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akira AJISAKA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3432) Cluster metrics have wrong Total Memory when there is reserved memory on CS
Date Mon, 01 Jun 2015 07:53:18 GMT

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

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

Thanks [~brahmareddy] for taking this issue. The patch seems to revert YARN-656. I'm thinking
that's not fine because it will break FairScheduler. This issue should fix CapacityScheduler
only.

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

Mime
View raw message