You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Yongjun Zhang (Jira)" <ji...@apache.org> on 2024/03/12 13:50:00 UTC

[jira] [Created] (YUNIKORN-2479) modified maxapplications attribute doesn't take effect until Yunikorn restart

Yongjun Zhang created YUNIKORN-2479:
---------------------------------------

             Summary: modified maxapplications attribute doesn't take effect until Yunikorn restart
                 Key: YUNIKORN-2479
                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2479
             Project: Apache YuniKorn
          Issue Type: Bug
          Components: core - scheduler
            Reporter: Yongjun Zhang
            Assignee: Yongjun Zhang


After increasing maxapplications limit in the config map (when there are quite some apps in accepted state in the queue), no changes happen in the number of running apps. The number increased to the new limit only after restarting Yunikorn.

This Jira is an attempt to make maxapplications change take effect without restarting yunikorn:
1. when maxapplications limit is increased, we should allow more accepted apps to enter running state; 

2. when maxapplications limit is decreased, we can let the apps continue until the number of running apps drops below the limit before running additional apps.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org