[
https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124947#comment-17124947
]
Peter Bacsko commented on YARN-9930:
------------------------------------
[~epayne] [~cane] [~snemeth] [~sunilg] could you guys share your opinion about
the POC?
Note that it actually does NOT interfere with the existing maxApps settings
because those is checked when the application is submitted. So the rejection
occurs immediately (see {{LeafQueue.validateSubmitApplication()}}). The
maxParallelApps check comes later, when we submit the application attempt to
the leaf queue.
Also, to avoid confusion I decided to call the new setting "maxParallelApps" to
avoid confusion (it's called "maxRunningApps" in FS).
> 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
> Attachments: YARN-9930-POC01.patch, YARN-9930-POC02.patch,
> YARN-9930-POC03.patch, YARN-9930-POC04.patch
>
>
> 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
