[ https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17129395#comment-17129395 ]
Peter Bacsko commented on YARN-9930: ------------------------------------ I did some testing with the patch - not with the upstream version, but backported to a certain Cloudera distro version then created a cluster. Results are very promising. Apps stay in ACCEPTED state as long as the number of running apps > maxParallelApps. Also, I stopped the active RM instance to activate the standby and the state of the applications was restored successfully, so RM/CS did not end up in an inconsistent state. !screenshot-1.png! Will do some more testing tomorrow, including max-parallel-apps settings for a particular user. > 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: Peter Bacsko > Priority: Major > Attachments: YARN-9930-001.patch, YARN-9930-002.patch, > YARN-9930-003.patch, YARN-9930-POC01.patch, YARN-9930-POC02.patch, > YARN-9930-POC03.patch, YARN-9930-POC04.patch, YARN-9930-POC05.patch, > screenshot-1.png > > > 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