[
https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967930#comment-16967930
]
Eric Payne commented on YARN-9930:
----------------------------------
bq. When we migrate from FS to CS, this difference will make users be confused.
[~cane] I see.
So, if I understand correctly, you are saying the following:
- in FS, submitting more than {{maxRunningApps}} per user will just leave the
apps waiting in the submitted state and will run them once other apps from that
user have completed.
- The CS will refuse to submitt more than {{Max Applications Per User}}.
Is that correct?
If it is a requirement to change this behavior in the CS, I would at least like
to see this change in behavior surrounded by a config property, with the
default being the old CS 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
