[
https://issues.apache.org/jira/browse/YUNIKORN-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved YUNIKORN-2630.
--------------------------------------
Fix Version/s: 1.6.0
1.5.2
Resolution: Fixed
> Release context lock in shim when processing config in the core
> ---------------------------------------------------------------
>
> Key: YUNIKORN-2630
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2630
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: shim - kubernetes
> Reporter: Wilfred Spiegelenburg
> Assignee: Wilfred Spiegelenburg
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.6.0, 1.5.2
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
