[YUNIKORN-2618] Streamline AsyncRMCallback UpdateAllocation

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.6.0
• Component/s: shim - kubernetes
• Labels: pull-request-available
• Target Version: 1.6.0
• Assignee: Yun Sun
• Reporter: Wilfred Spiegelenburg
• Created: 09/May/24 06:36
• Updated: 22/May/24 21:08
• Resolved: 22/May/24 21:07

Description

if task is not found, a nil is returned from context.getTask in  for response.New processing we should just log that fact and proceed to the next alloc. Simplifies the flow as we never need to check for a. nil task. We should never have a pod in the cache that does not exist as a task on an application.

We retrieve the application using the application ID from the response to never use the object. We only use the application ID to pass into an event. The context event handler then does the exact same lookup again to process the event on the app.

We need to become much smarter in this area, double or triple lookups, generate async events that just change the state of the app or task or kick off another event.

Issue Links

• links to: GitHub Pull Request #846