[
https://issues.apache.org/jira/browse/IGNITE-19967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-19967:
---------------------------------
Description:
In https://issues.apache.org/jira/browse/IGNITE-19061 we have provided and
later implemented algorithm for restoring zones states after restart.
In https://issues.apache.org/jira/browse/IGNITE-19778 and other tickets new
invariants for recovery were introduced, in particular, in the new proposal
node state is recovered not until applied revision, but until some higher
revision, which brings inconsistency for restoring Distribution Zone Manager
because the process was based on saving states to the Vault and on mechanism
with restoring from the Vault. Previously we could based our recovery on the
fact, that all events, that node missed during absence, will be applied to
starting from metastorage applied revision, but in the new recovery process,
node receives only snapshot of the data and we cannot restore the history of
data nodes related events.
In this task we need to provide a new approach, taking into account new
circumstances.
was:
In https://issues.apache.org/jira/browse/IGNITE-19061 we have provided and
later implemented algorithm for restoring zones states after restart.
In https://issues.apache.org/jira/browse/IGNITE-19778 and other tickets new
invariants for recovery were introduced, in particular, in the new proposal
node state is recovered not until applied revision, but until some higher
revision, which brings inconsistency for restoring Distribution Zone Manager
because the process was based on saving states to the Vault and on previous
mechanism with restoring from the Vault
In this task we need to provide a new approach, taking into account new
circumstances.
> Design restart of Distribution Zone Manager in accordance with the new local
> recovery process
> ---------------------------------------------------------------------------------------------
>
> Key: IGNITE-19967
> URL: https://issues.apache.org/jira/browse/IGNITE-19967
> Project: Ignite
> Issue Type: Task
> Reporter: Mirza Aliev
> Assignee: Mirza Aliev
> Priority: Major
> Labels: ignite-3
>
> In https://issues.apache.org/jira/browse/IGNITE-19061 we have provided and
> later implemented algorithm for restoring zones states after restart.
> In https://issues.apache.org/jira/browse/IGNITE-19778 and other tickets new
> invariants for recovery were introduced, in particular, in the new proposal
> node state is recovered not until applied revision, but until some higher
> revision, which brings inconsistency for restoring Distribution Zone Manager
> because the process was based on saving states to the Vault and on mechanism
> with restoring from the Vault. Previously we could based our recovery on the
> fact, that all events, that node missed during absence, will be applied to
> starting from metastorage applied revision, but in the new recovery process,
> node receives only snapshot of the data and we cannot restore the history of
> data nodes related events.
> In this task we need to provide a new approach, taking into account new
> circumstances.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
