[
https://issues.apache.org/jira/browse/IGNITE-19543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy resolved IGNITE-19543.
----------------------------------------
Resolution: Invalid
Catalog currently has recovery on start, but, according to [~korlov] , it's
only for refilling in-memory structures of the Catalog itself. Catalog should
start first, so no other components will have ability to register listeners
before it recovers. This is by design: other components should go to the
Catalog explicitly on start instead of relying on listeners.
> Implement replay-events-on-local-snapshot logic for Catalog over metastorage
> on start
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-19543
> URL: https://issues.apache.org/jira/browse/IGNITE-19543
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Transferring catalog from configuration to meta storage may require
> additional work on node recovery in order to start local entities such as
> tables and indexes. Currently it’s implemented through configuration
> listeners that are fired when configuration locally restores on top of vault.
> Basically: LocalRestart[Vault → Configuration ->… ->
> fireConfigurationNotifications ] will restart all local entities in exact the
> same way (by calling exact the same cfg listeners) like distribution events
> do. Meta storage lacks such replay-events-on-local-snapshot logic that
> probably should be implemented somehow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
