[IGNITE-8719] Index left partially built if a node crashes during index create or rebuild

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.11
• Component/s: sql
• Release Note: Restart rebuild indexes, if they were not rebuilt, on node restart / reactivation.
• Ignite Flags: Release Notes Required
• Assignee: Kirill Tkalenko
• Reporter: Alexey Goncharuk
• Reviewer: Andrey Mashenkov
• Created: 06/Jun/18 09:41
• Updated: 08/Jun/21 09:47
• Resolved: 07/Jun/21 09:11

Description

Currently, we do not have any state associated with the index tree. Consider the following scenario:
1) Start node, put some data
2) start CREATE INDEX operation
3) Wait for a checkpoint and stop node before index create finished
4) Restart node
Since the checkpoint finished, the new index tree will be persisted to the disk, but not all data will be present in the index.

We should somehow store information about initializing index tree and mark it valid only after all data is indexed. The state should be persisted as well.

Issue Links

• is a child of: IGNITE-11075 Index rebuild procedure over cache partition file
• is related to: IGNITE-14702 Inconsistency of the new index when the node falls / deactivates
• is related to: IGNITE-14625 Make DurableBackgroundTask return future
• is required by: IGNITE-14254 Graceful stop rebuilding indexes when deactivating a cluster
• relates to: IGNITE-14321 Forced index rebuilding does not work correctly
• links to: GitHub Pull Request #5223
• links to: GitHub Pull Request #9090
• links to: MTCGA
• links to: Team City
• links to: TeamCity :: PDS (Indexing / WAL & Recovery)