[
https://issues.apache.org/jira/browse/YUNIKORN-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829568#comment-17829568
]
Peter Bacsko edited comment on YUNIKORN-2510 at 3/21/24 2:00 PM:
-----------------------------------------------------------------
-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.-
EDIT: not relevant.
was (Author: pbacsko):
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.
> EDIT: #1 doesn't seem to be a problem. After further reviewing the code, we
> only start the timer after the first allocation. So looks like we need to
> decide whether immediate creation of PH pods is OK or not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
