[
https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265945#comment-17265945
]
Ilya Kasnacheev commented on IGNITE-13976:
------------------------------------------
[~av] I have seen a few cases where the cluster is in inconsistent state after
disabling or enabling WAL (such as, refusing to change WAL status due to "nodes
returned different results") so it's not "nice to have". I would say that it is
a blocker for WAL enable/disable feature in Apache Ignite.
It would be very helpful if you could try the reproducer along with my
approaches to fix it, tell me whether they have any merit. I don't persuade you
to provide a complete fix, I could do that myself once I understand where to
dig.
> 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: Ilya Kasnacheev
> Priority: Major
>
> 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)
