Peter Bacsko commented on YARN-9930:

OK, I did some extra testing.
 # Limit max-parallel-apps to 2, submit 4 apps, then refresh it to 4. Result: 
pending apps transitioned to Running state.
 # Limit max-parallel-apps to 4, submit 4 apps, then refresh it to 2. Result: 
running apps were still running, but new apps stayed in Accepted state. >From 
that point on, only 2 apps were allowed to run at the same time.

I also did other manual tests:
 # Limit max-parallel-apps to 2 for all users, then override to 4 for a 
specific user. Result: specific user could run 4 apps. Other user could only 
run 2 apps.
 # Limit max-parallel-apps to 2 for the "root" queue and submit apps to a leaf 
queue. Result: leaf queue could only run 2 apps in parallel, which is expected.

To me it looks functionally correct. 

> 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-004.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

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to