[jira] [Commented] (YUNIKORN-2510) Placeholder processing starts immediately despite maxApplications limit

["Peter Bacsko (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YUNIKORN-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829568#comment-17829568 ] 

Peter Bacsko commented on YUNIKORN-2510:
----------------------------------------

I'm not sure if it's realistic or not, but #1 can also cause to reach the namespace quota more quickly if there's any. AFAIK we don't recommend using it with Yunikorn.

> Placeholder processing starts immediately despite maxApplications limit
> -----------------------------------------------------------------------
>
>                 Key: YUNIKORN-2510
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2510
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: core - scheduler
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>
> If the maxApplication limit is hit inside {{Application.tryAllocate()}}, we still create the placeholder pods in the shim. This has two consequences:
> 1. Although they stay in Pending state, these pods still consume resources in the cluster, because they are tracked by the API server. 
> 2. Placeholder timer is started immediately. If the timeout expires, it affects the application, even if it's not in a runnable state.
> #2 is more problematic and needs to be addressed. #1 is up to discussion.



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

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