[YUNIKORN-460] Handle app reservation timeout

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.10
• Component/s: shim - kubernetes
• Labels: pull-request-available
• Assignee: Kinga Marton
• Reporter: Weiwei Yang
• Created: 18/Nov/20 05:23
• Updated: 21/Jan/22 21:48
• Resolved: 08/Mar/21 23:49

Description

When an app is configured with a timeout, that determines the maximum time permitted to stay in the Reserving phase. If that times out, then all the existing placeholders should be deleted and the application will be scheduled normally. This timeout is needed because otherwise an app’s partial placeholders may occupy cluster resources and they are wasted.

See more in this doc

Issue Links

• relates to: YUNIKORN-567 Queue resources are not cleaned up after placeholder cleanup
• relates to: YUNIKORN-572 terminated app move causes deadlock
• links to: GitHub Pull Request #32
• links to: GitHub Pull Request #231
• links to: GitHub Pull Request #250