[
https://issues.apache.org/jira/browse/IGNITE-13366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-13366:
-------------------------------------
Issue Type: New Feature (was: Task)
> Prohibit unconditional automatic deletion of data files if WAL was disabled
> prior to node's shutdown
> ----------------------------------------------------------------------------------------------------
>
> Key: IGNITE-13366
> URL: https://issues.apache.org/jira/browse/IGNITE-13366
> Project: Ignite
> Issue Type: New Feature
> Components: persistence
> Affects Versions: 2.8.1
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Critical
> Fix For: 2.10
>
> Original Estimate: 168h
> Time Spent: 10m
> Remaining Estimate: 167h 50m
>
> If node with persistence is stopped when WAL was disabled for a cache (no
> matters because of rebalancing in progress or by explicit user request) on
> next node start all data files of that cache are removed automatically and
> unconditionally.
> This behavior may be unexpected for users as they may not understand all
> consequences of disabling WAL locally (for rebalancing) or globally (via
> IgniteCluster API call). Also it is not smart enough as there is no point in
> deleting consistent data files.
> We should change this behavior to the following list: no automatic deletions
> whatsoever. If data files are consistent (equivalent to: no checkpoint was
> running when node was stopped) start up normally. If data files are
> corrupted, don't let the node start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
