[IGNITE-14321] Forced index rebuilding does not work correctly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.11
• Component/s: sql
• Release Note: Fixes for the ability to force rebuild indexes for caches.
• Ignite Flags: Release Notes Required
• Assignee: Kirill Tkalenko
• Reporter: Kirill Tkalenko
• Reviewer: Taras Ledkov
• Created: 16/Mar/21 06:43
• Updated: 27/May/22 16:27
• Resolved: 12/Apr/21 14:50

Description

At the moment, it is not possible to force an index rebuild twice (or more) even if the first run fails, and this also applies to command control.sh --cache indexes_force_rebuild.

Thus, we need to fix:

• GridCacheDatabaseSharedManager#forceRebuildIndexes
• CacheIndexesForceRebuild#execute

Issue Links

• blocks: IGNITE-14469 Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
• is related to: IGNITE-8719 Index left partially built if a node crashes during index create or rebuild
• relates to: IGNITE-6628 Make possible to rebuild all SQL indexes programmatically with enabled persistence.
• requires: IGNITE-14254 Graceful stop rebuilding indexes when deactivating a cluster
• links to: Dev list
• links to: GitHub Pull Request #8962