[
https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318005#comment-17318005
]
Ilya Kasnacheev commented on IGNITE-13976:
------------------------------------------
https://github.com/apache/ignite/pull/8643 LGTM now, the only red flag is
misplaced cache context access in ClusterCachesInfo
[~sergeychugunov]
> 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
> Time Spent: 10m
> 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)
