[IGNITE-19778] Restore components state on metastorage recovery

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0
• Labels: ignite-3
• Epic Link: Metastorage Compaction
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Semyon Danilov
• Reporter: Semyon Danilov
• Created: 20/Jun/23 09:54
• Updated: 04/Sep/24 16:10
• Resolved: 12/Jul/23 08:05

Description

Upon metastorage signalling (https://issues.apache.org/jira/browse/IGNITE-19777) that certain revision that was available when recovery started is achieved by the local metastorage storage, components should restore their state using a "snapshot" of the data with that specific revision. For example, TableManager might want to start tables that it sees in that snapshot. Note that tables that are missing from the data snapshot, must be destroyed as they are now obsolete.
So state must be restored and outdated remains of the previous state must be cleared out.

Issue Links

• breaks: IGNITE-19965 TableManager recovery
• breaks: IGNITE-19967 Design restart of Distribution Zone Manager in accordance with the new local recovery process
• is related to: IGNITE-19955 Fix create zone on restart rewrites existing data nodes because of trigger key inconsistnecy
• links to: GitHub Pull Request #2266