[
https://issues.apache.org/jira/browse/YUNIKORN-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888456#comment-17888456
]
Shravan Achar commented on YUNIKORN-2910:
-----------------------------------------
With this patch applied, the same issue is seen. With the patch, the
[^state-dump-1.6-context-locking-after-2.json] is attached. But with the same
test setup, the [^state-dump-after-1.5.2.json] on 1.5.2 indicates accurate
calculations.
> 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
>
> Attachments: state-dump-1.6-context-locking-after-2.json,
> state-dump-after-1.5.2.json
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
