[IGNITE-13366] Special mode for maintenance of Ignite node. Employing Maintenance Mode for clearing corrupted PDS files.

• Type: New Feature
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.8.1
• Fix Version/s: 2.10
• Component/s: persistence
• Labels: IEP-53
• Release Note: Special mode to perform maintenance tasks is introduced. Ignite node starts up but does not join the rest of the cluster and allows user to perform health-checks, resolve issues or do other maintenance.
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Sergey Chugunov
• Reporter: Sergey Chugunov
• Created: 17/Aug/20 12:34
• Updated: 06/Aug/21 15:24
• Resolved: 15/Oct/20 06:46

Description

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.

Issue Links

• causes: IGNITE-13664 GridCommandHandlerTest.testPersistenceCleanCorruptedCachesCommand fails on Windows platform
• links to: GitHub Pull Request #8189
• links to: GitHub Pull Request #8325
• mentioned in: Page Loading...