[YUNIKORN-2174] placeholder count in partition incorrect

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.5.0
• Component/s: core - scheduler
• Labels: pull-request-available
• Target Version: 1.5.0
• Assignee: Wilfred Spiegelenburg
• Reporter: Wilfred Spiegelenburg
• Created: 22/Nov/23 06:02
• Updated: 20/Mar/24 14:32
• Resolved: 27/Nov/23 14:00

Description

Placeholder releases are handled specially as it could trigger a replacement and not just a removal of the placeholder. The placeholder count in the partition that we use to skip the replacement cycle is adjusted for each replacement.

However, If a placeholder gets deleted on K8s, times out or gets preempted the termination type is different. The placeholder gets released as any other allocation but we still need to adjust the placeholder counter.

The impact of this issue is a less optimal scheduling cycle as the counter will never reach 0 anymore. Beside that there is no impact.

Issue Links

• is caused by: YUNIKORN-1886 Optimize scheduling cycle if there's no placeholder allocation or reservation
• Testing discovered: YUNIKORN-2197 remove FitInMaxUndef from node code
• links to: GitHub Pull Request #732