[
https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319456#comment-17319456
]
Ignite TC Bot commented on IGNITE-13976:
----------------------------------------
{panel:title=Branch: [pull/8643/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8643/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}PDS 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5963537]]
* {color:#013220}IgnitePdsTestSuite: WalEnableDisableWithRestartsTest.test -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5963157&buildTypeId=IgniteTests24Java8_RunAll]
> 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: 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)
