You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2024/10/10 15:44:00 UTC
[jira] [Resolved] (YUNIKORN-2910) Data corruption due to insufficient shim context locking
[ https://issues.apache.org/jira/browse/YUNIKORN-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Condit resolved YUNIKORN-2910.
------------------------------------
Fix Version/s: 1.7.0
1.6.1
Resolution: Fixed
Merged to master and cherry-picked to branch-1.6.
> Data corruption due to insufficient shim context locking
> --------------------------------------------------------
>
> Key: YUNIKORN-2910
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2910
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Affects Versions: 1.6.0
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.7.0, 1.6.1
>
>
> We need to restore the context locking that was removed in YUNIKORN-2629. Without it, multiple K8s events of different types may be processed in parallel. Specifically, pod and node events being processed simultaneously is not safe, and results in data corruption.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org