Wangda Tan commented on YARN-3434:

I think a maybe simpler/more consistent approach to solve this problem is 
considering reserved resource for each user when computing user-limit. My 
understanding for reserved resource is, it should be counted as "usage", we 
added reserved resource to queue's usage but we don't add them to user's usage. 
But I think we should do the same thing for user: When the more 
resource/containers a user reserves, the more opportunity the user will get, 
and it will block other users in the same queue receives resources.

Is there any side effect if we doing this?

> 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

Reply via email to