You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ilya Kasnacheev (Jira)" <ji...@apache.org> on 2021/01/11 16:09:00 UTC
[jira] [Updated] (IGNITE-13976) WAL disable/enable with node
restarts results in mismatching state, data loss
[ https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Kasnacheev updated IGNITE-13976:
-------------------------------------
Description:
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.
was:
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 attached reproducer.
> 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)