[
https://issues.apache.org/jira/browse/IGNITE-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov updated IGNITE-19965:
------------------------------------
Description:
*Motivation*
At the moment TableManager has the logic, which based on the two assumptions:
- on the recovery we will receive the all needed configuration updates with
appropriate revision numbers
- the same will be true for the all metastore updates
But after the <issue> both assumptions will be wrong.
*Definition of done*
- during the TableManager start all needed metastore data like rebalance keys
and stable assignments must be manually updated from metastore and appropriate
processing executed.
- the logic which based on the configuration/metastore revision comparing (if
exists, but it look like it is migrated to DistributionZoneManager already)
must be fixed
> TableManager recovery
> ---------------------
>
> Key: IGNITE-19965
> URL: https://issues.apache.org/jira/browse/IGNITE-19965
> Project: Ignite
> Issue Type: Task
> Reporter: Kirill Gusakov
> Priority: Major
>
> *Motivation*
> At the moment TableManager has the logic, which based on the two assumptions:
> - on the recovery we will receive the all needed configuration updates with
> appropriate revision numbers
> - the same will be true for the all metastore updates
> But after the <issue> both assumptions will be wrong.
> *Definition of done*
> - during the TableManager start all needed metastore data like rebalance keys
> and stable assignments must be manually updated from metastore and
> appropriate processing executed.
> - the logic which based on the configuration/metastore revision comparing (if
> exists, but it look like it is migrated to DistributionZoneManager already)
> must be fixed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
