[
https://issues.apache.org/jira/browse/YARN-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212015#comment-14212015
]
Sandy Ryza commented on YARN-2811:
----------------------------------
This looks almost good to go - the last thing is that we should use
Resources.fitsIn instead of Resources.lessThanOrEqual(RESOURCE_CALCULATOR...),
as the latter will only consider memory.
> 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, YARN-2811.v5.patch,
> YARN-2811.v6.patch, YARN-2811.v7.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)
