[
https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018021#comment-17018021
]
Sunil G commented on YARN-9930:
-------------------------------
[~cane] Thanks for working on this. and thanks [~epayne] [~pbacsko] for adding
your thoughts.
I agree with [~epayne] here, and we can protect this additional change of
behaviour with a boolean like existing _*MaxRunningAppsEnforcer*_ in FS (may
be with some good refactoring, if possible). Then our computed Max Apps Per
User will be enforced by default with a value of MaxRunningAppsEnforcer=true.
If user changes MaxRunningAppsEnforcer to false, then we can accept the
submission of apps and wait in the queue for scheduling.
Could you please share your proposed patch based on the discussion had here.
> 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
