[
https://issues.apache.org/jira/browse/YARN-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976507#comment-15976507
]
Sunil G commented on YARN-2113:
-------------------------------
Ideally we could do this by skipping a container, provided i keep a running
resource counter per user. However as mentioned by [~leftnoteasy], UL can be
changed just after this selection. I think we can try to keep this simple by
skipping _one container_ or adding a deadzone.
With directed graph, we still need to worry about multiple users. But from
scheduler point of view, it allocates one more container to same user's app
after preemption and bring the used capacity above to UL. A doubt here, if
there are some under-served user's apps are present, do we need to give that
extra container for same app which pushes the used cap above UL?
We do something similar while activating apps with AM resource percentage to
see amIfUsed is going for that limit. May be something similar here.
> Add cross-user preemption within CapacityScheduler's leaf-queue
> ---------------------------------------------------------------
>
> Key: YARN-2113
> URL: https://issues.apache.org/jira/browse/YARN-2113
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: scheduler
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Sunil G
> Attachments:
> TestNoIntraQueuePreemptionIfBelowUserLimitAndDifferentPrioritiesWithExtraUsers.txt,
> YARN-2113.0001.patch, YARN-2113.0002.patch, YARN-2113.0003.patch,
> YARN-2113.0004.patch, YARN-2113.0005.patch, YARN-2113.0006.patch,
> YARN-2113.0007.patch, YARN-2113.v0.patch
>
>
> Preemption today only works across queues and moves around resources across
> queues per demand and usage. We should also have user-level preemption within
> a queue, to balance capacity across users in a predictable manner.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
