[
https://issues.apache.org/jira/browse/IGNITE-19778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-19778:
-------------------------------------
Epic Link: IGNITE-20166
> Restore components state on metastorage recovery
> ------------------------------------------------
>
> Key: IGNITE-19778
> URL: https://issues.apache.org/jira/browse/IGNITE-19778
> Project: Ignite
> Issue Type: Bug
> Reporter: Semyon Danilov
> Assignee: Semyon Danilov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
