You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2020/06/03 13:03:00 UTC
[jira] [Commented] (YARN-9930) Support max running app logic for
CapacityScheduler
[ https://issues.apache.org/jira/browse/YARN-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124932#comment-17124932 ]
Peter Bacsko commented on YARN-9930:
------------------------------------
Attached POC v4 with a new unit tests which verifies the new functionality. Still a POC because there are failing UTs.
TODO
* fix failing UTs (most likely mocking should be fine tuned)
* fix checkstyle
* more tests for the new feature (eg. user limit exceeded)
* check visibility of new methods
* add tests for CSMaxRunningAppsEnforcer (likely a copy-paste + edits from TestMaxRunningAppsEnforcer)
> 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
> Attachments: YARN-9930-POC01.patch, YARN-9930-POC02.patch, YARN-9930-POC03.patch, YARN-9930-POC04.patch
>
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org