[
https://issues.apache.org/jira/browse/YARN-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tristan Stevens updated YARN-5502:
----------------------------------
Attachment: yarn-rm.png
> RM web page shows incorrect max pool size for nested pools
> ----------------------------------------------------------
>
> Key: YARN-5502
> URL: https://issues.apache.org/jira/browse/YARN-5502
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler, webapp
> Affects Versions: 2.6.0, 2.7.0
> Reporter: Tristan Stevens
> Attachments: yarn-rm.png
>
>
> The scheduler page in the webapp incorrectly shows child pools' maximum sizes
> without first considering the maximum size of the parent.
> For example:
> Parent Queue AppD has Weight 100, Max: 1 CPU 100MB RAM
> Child Queue AppD.Child2 has Weight 1 Max: 100 CPU 1PB RAM
> In YARN RM, the max resources for AppD.Child2 shows up as being larger than
> the max resources for AppD, although the execution in the scheduler here is
> actually fine. In the image attached AppE has the same maximum as AppD, yet
> AppD.Child2 shows as having Max Resources well above that of AppE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
