[
https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16973280#comment-16973280
]
zhoukang commented on YARN-9930:
--------------------------------
[~pbacsko]Thanks. The background is that in our production cluster we want to
upgrade hadoop version to 3.x, and we used FairScheduler before.
Now we want to use CapacityScheduler in new version 3.x.
If we want to migrate from FS to CS , this behavior will be confused.
[~epayne][~pbacsko]I agree with the point.Add a config like
bq. "yarn.scheduler.capacity.maxrunningapps.reject"
> 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: [email protected]
For additional commands, e-mail: [email protected]
