[
https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203685#comment-14203685
]
Sandy Ryza commented on YARN-2811:
----------------------------------
I just realized an issue with this. maxResources can be set on parent queues
as well, so checking the maxResources of the leaf queue that the app is part of
is not enough. Sorry for not catching this earlier.
A couple more style nitpicks: remember to keep lines close to 80 characters and
to put a space after the double slashes that initiate a comment. Also, FSQueue
has a getMaxShare method, so you don't need to go to the trouble of getting the
name and passing it to the map in the allocation configuration.
> Fair Scheduler is violating max memory settings in 2.4
> ------------------------------------------------------
>
> Key: YARN-2811
> URL: https://issues.apache.org/jira/browse/YARN-2811
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Siqi Li
> Assignee: Siqi Li
> Attachments: YARN-2811.v1.patch, YARN-2811.v2.patch,
> YARN-2811.v3.patch, YARN-2811.v4.patch
>
>
> This has been seen on several queues showing the allocated MB going
> significantly above the max MB and it appears to have started with the 2.4
> upgrade. It could be a regression bug from 2.0 to 2.4
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
