[YUNIKORN-462] Streamline core to shim update on allocation change

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: core - scheduler, shim - kubernetes
• Labels: pull-request-available
• Assignee: Manikandan R
• Reporter: Wilfred Spiegelenburg
• Created: 18/Nov/20 08:21
• Updated: 04/May/22 23:52
• Resolved: 24/Feb/22 23:33

Description

Currently in the scheduler we have two updates that get send to the shim when an allocation is added or released:

• event to shim RM event handler to allocate
• reconciler plugin to update the shim caches

Before YUNIKORN-317 one update was made in the cace the other in the scheduler. Now they are both in the scheduler in quick succession. The cache update in the shim is needed to make sure that the predicates are seeing the correct info. The event does the real bind etc of the allocation on the node.

We should be able to fold the two calls into one call. However this requires changes on both sides and might even impact the SI as it will likely become a synced event call.

Issue Links

• causes: YUNIKORN-557 change log level for ambiguous sync failure message
• causes: YUNIKORN-1097 RMProxy DEBUG cannot log event with channel
• causes: YUNIKORN-1099 Deadlock in Application.notifyRMAllocationReleased()
• links to: GitHub Pull Request #58
• links to: GitHub Pull Request #344
• links to: GitHub Pull Request #350