[YUNIKORN-1985] possible log spew in application object in tryAllocate()

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: core - scheduler
• Labels: newbie pull-request-available
• Assignee: Kuan Po Tseng
• Reporter: Wilfred Spiegelenburg
• Created: 14/Sep/23 06:24
• Updated: 17/Jan/24 15:45
• Resolved: 26/Oct/23 14:45

Description

If a pod has a required node and cannot be scheduled we keep on attempting the pod placement and cause a log spew:

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"} 

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.

Issue Links

• causes: YUNIKORN-2320 Package-level loogging breaks custom logging configuration
• links to: GitHub Pull Request #663