[
https://issues.apache.org/jira/browse/YARN-10802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17369503#comment-17369503
]
Benjamin Teke edited comment on YARN-10802 at 6/25/21, 2:37 PM:
----------------------------------------------------------------
[~epayne], thanks for the clarification. This actually came from a customer
request, they wanted to allow 100+ concurrent (and active) users in a single
queue simultaneously for some reason, and the change itself didn't seem to be a
big/intrusive one, as it is still possible to use whole numbers.
As for the observation: this is interesting. Personally I have little to no
experience with heavily-used multi tenant queues, but this growth limit is
certainly something to keep in mind.
was (Author: bteke):
[~epayne], thanks for the clarification. This actually came from a customer
request, they wanted to allow 100+ concurrent (and active) users in a single
queue simultaneously for some reason, and the change itself didn't seem to be a
big/intrusive one.
As for the observation: this is interesting. Personally I have little to no
experience with heavily-used multi tenant queues, but this growth limit is
certainly something to keep in mind.
> Change Capacity Scheduler minimum-user-limit-percent to accept decimal values
> -----------------------------------------------------------------------------
>
> Key: YARN-10802
> URL: https://issues.apache.org/jira/browse/YARN-10802
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacity scheduler
> Reporter: Benjamin Teke
> Assignee: Benjamin Teke
> Priority: Major
> Fix For: 3.4.0
>
> Attachments: YARN-10802.001.patch, YARN-10802.002.patch,
> YARN-10802.003.patch, YARN-10802.004.patch
>
>
> Capacity Scheduler's minimum-user-limit-percent only accepts integers, which
> means at most 100 users can use a single queue fairly. Using decimal values
> could solve this problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
