[
https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970417#comment-16970417
]
Eric Payne commented on YARN-9930:
----------------------------------
The Max Apps Per User Setting exists in CS, but it's
a calculated value and not directly configurable. It's calculated based on the
Max Apps per Queue, the User Limit Factor, and the Minimum User Limit Percent,
which are all directly configurable. To see the current value of the Max Apps
Per User, go to the CS UI and click on the twisty of any queue. In the CS, any
user who reaches that value will not be allowed to submit any more apps until
one of their running apps completes. For CS's backward compatibility, I feel
that it's important to keep that as the default behavior.
> Support max running app logic for CapacityScheduler
> ---------------------------------------------------
>
> Key: YARN-9930
> URL: https://issues.apache.org/jira/browse/YARN-9930
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler, capacityscheduler
> Affects Versions: 3.1.0, 3.1.1
> Reporter: zhoukang
> Assignee: zhoukang
> Priority: Major
>
> In FairScheduler, there has limitation for max running which will let
> application pending.
> But in CapacityScheduler there has no feature like max running app.Only got
> max app,and jobs will be rejected directly on client.
> This jira i want to implement this semantic for CapacityScheduler.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
