[ https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970421#comment-16970421 ]
Peter Bacsko commented on YARN-9930: ------------------------------------ [~epayne] thanks for explaining - now it's clear. I do agree that it's important to keep backward compatibility. I guess we can introduce a boolean property like "yarn.scheduler.capacity.maxrunningapps.reject" with default value "true". > 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