[ https://issues.apache.org/jira/browse/YARN-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613507#comment-15613507 ]
Hudson commented on YARN-3432: ------------------------------ SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10711 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/10711/]) YARN-3432. Cluster metrics have wrong Total Memory when there is (carlo curino: rev 892a8348fceb42069ea9877251c413fe33415e16) * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/dao/ClusterMetricsInfo.java > 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 > Labels: oct16-easy > Fix For: 2.8.0 > > Attachments: YARN-3432-002.patch, YARN-3432-003.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) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org