[
https://issues.apache.org/jira/browse/YUNIKORN-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko resolved YUNIKORN-1985.
------------------------------------
Fix Version/s: 1.4.0
Resolution: Fixed
Merged to master, thanks [~brandboat] for the contribution.
> possible log spew in application object in tryAllocate()
> --------------------------------------------------------
>
> Key: YUNIKORN-1985
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1985
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler
> Reporter: Wilfred Spiegelenburg
> Assignee: Kuan-Po Tseng
> Priority: Minor
> Labels: newbie, pull-request-available
> Fix For: 1.4.0
>
>
> If a pod has a required node and cannot be scheduled we keep on attempting
> the pod placement and cause a log spew:
> {code:java}
> 2023-06-15T10:42:43.546Z WARN objects/application.go:993 required
> node is not found (could be transient) {"application ID":
> "yunikorn-ag-ecp12s-1-autogen", "allocationKey":
> "b51b0a36-214a-4a12-a285-d4319f4b5254", "required node": "worker-31.XXXX"}
> {code}
> This can happen if a daemonset pod is created and the node is not in the
> right state.
> We should move this to debug or have a rate limit on how often we log this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
