Peter Bacsko created YUNIKORN-2510: -------------------------------------- Summary: 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
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-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org