[
https://issues.apache.org/jira/browse/YARN-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil G updated YARN-7254:
--------------------------
Attachment: YARN-7254.YARN-5881.003.patch
Almost fixed the mentioned comments. Updating a patch.
bq.REST API (should we add -mb suffix to memory as well? And change vCores to
vcores)
In {{org.apache.hadoop.yarn.server.resourcemanager.webapp.dao.ResourceInfo
}}, we have *toString* defined as
{code}
@Override
public String toString() {
return "<memory:" + memory + ", vCores:" + vCores + ">";
}
{code}
If we change this, it will impact REST o/p for all metrics etc from RM. I think
a backward compatibility issue is there if we do this.
bq.Configured Capacity: <memory:6000, vCores:5> (100.0%) (Should this be
vcore=8?).
Configured was 8GB and 8 Cores and cluster capacity was 5.8GB and 12 cores.
Since this value is lesser when we try with Default Calculator,
*effectiveMinRatio* is kicking in and reducing the whole res down.
> UI and metrics changes related to absolute resource configuration
> -----------------------------------------------------------------
>
> Key: YARN-7254
> URL: https://issues.apache.org/jira/browse/YARN-7254
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: YARN-7254.001.patch, YARN-7254.002.patch,
> YARN-7254.YARN-5881.002.patch, YARN-7254.YARN-5881.003.patch
>
>
> Impact on UI and metrics related to absolute resource configuration on CS
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
