[
https://issues.apache.org/jira/browse/YARN-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497055#comment-14497055
]
Thomas Graves commented on YARN-3434:
-------------------------------------
I agree with Both section. I'm not sure I completely follow the Only section.
Are you suggesting we change the patch to modify ResourceLimits and pass down
rather then using the LimitsInfo class? If so that won't work, at least not
without adding the shouldContinue flag to it. Unless you mean keep LimitsInfo
class for use locally in assignContainers and then pass ResourceLimits down to
assignContainer with the value of amountNeededUnreserve as the limit. That
wouldn't really change much exception the object we pass down through the
functions.
> Interaction between reservations and userlimit can result in significant ULF
> violation
> --------------------------------------------------------------------------------------
>
> Key: YARN-3434
> URL: https://issues.apache.org/jira/browse/YARN-3434
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 2.6.0
> Reporter: Thomas Graves
> Assignee: Thomas Graves
> Attachments: YARN-3434.patch
>
>
> ULF was set to 1.0
> User was able to consume 1.4X queue capacity.
> It looks like when this application launched, it reserved about 1000
> containers, each 8G each, within about 5 seconds. I think this allowed the
> logic in assignToUser() to allow the userlimit to be surpassed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
