[
https://issues.apache.org/jira/browse/IGNITE-22470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-22470:
-------------------------------------
Reviewer: Philipp Shergalis (was: Roman Puchkovskiy)
> Switch IndexMetaStorage from Vault to MetaStorage
> -------------------------------------------------
>
> Key: IGNITE-22470
> URL: https://issues.apache.org/jira/browse/IGNITE-22470
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After implementing IGNITE-22367, I realized that there may be a situation
> when we need index metadata locally, but it won’t be there. To avoid such
> situations and maintain consistency in the presence of index metadata while
> it exists in the system, we need to change the storage of index metadata from
> Vault to MetaStorage.
> An example scenario that might reproduce the problem:
> # Node A started building an index.
> # There is no transaction load.
> # The low watermark has been updated and removed the version of the catalog
> in which the index appeared.
> # Node B entered the cluster and began applying changes from node A.
> # Index construction is complete.
> # The cluster has restarted.
> # Node B is experiencing a disaster recovery and needs to build the index
> locally.
> # The version in which the index appeared on node B is missing - there will
> be errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
