[jira] [Comment Edited] (IGNITE-13976) WAL disable/enable with node restarts results in mismatching state, data loss

["Sergey Chugunov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319464#comment-17319464 ] 

Sergey Chugunov edited comment on IGNITE-13976 at 4/12/21, 2:01 PM:
--------------------------------------------------------------------

[~ilyak],

I fixed your comment about manipulating cache context in ClusterCachesInfo, new and existing tests look good.

Merged fix to master branch in commit *71dbf16cd23af91f25e65824a73d2cc438747b30*.


was (Author: sergeychugunov):
[~ilyak],

I fixed your comment about manipulating cache context in ClusterCachesInfo, new and existing tests look good.

Merging the fix into master branch.

> WAL disable/enable with node restarts results in mismatching state, data loss
> -----------------------------------------------------------------------------
>
>                 Key: IGNITE-13976
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13976
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 2.9.1
>            Reporter: Ilya Kasnacheev
>            Assignee: Sergey Chugunov
>            Priority: Critical
>             Fix For: 2.11
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> If you try to enable/disable WAL on unstable topology, you will get to state when WAL status is undefined, nodes might have different wall status and the only way to fix it is to restart the cluster, which will lead to data loss because ignite removes data if WAL is disabled on restart.
> See the reproducer in PR.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)