[YUNIKORN-2630] Release context lock in shim when processing config in the core

• Type: Improvement
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.6.0, 1.5.2
• Component/s: shim - kubernetes
• Labels: pull-request-available
• Target Version: 1.6.0, 1.5.2
• Assignee: Wilfred Spiegelenburg
• Reporter: Wilfred Spiegelenburg
• Created: 17/May/24 02:07
• Updated: 21/May/24 14:37
• Resolved: 21/May/24 14:37

Description

When an change comes in for a the configmaps we process the change under a context lock as we need to merge the two configmaps.

We keep this lock even if all the work is done in the shim and processing has been transferred to the core. This is unneeded as the core has its own locking an serialisation of the changes.

Issue Links

• relates to: YUNIKORN-2629 Adding a node can result in a deadlock
• links to: GitHub Pull Request #842