You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mirza Aliev (Jira)" <ji...@apache.org> on 2023/10/10 15:43:00 UTC
[jira] [Updated] (IGNITE-20604) Reimplement CausalityDataNodesEngine#dataNodes according to Catalog and recovery changes
[ https://issues.apache.org/jira/browse/IGNITE-20604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mirza Aliev updated IGNITE-20604:
---------------------------------
Epic Link: IGNITE-20611 (was: IGNITE-20166)
> Reimplement CausalityDataNodesEngine#dataNodes according to Catalog and recovery changes
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-20604
> URL: https://issues.apache.org/jira/browse/IGNITE-20604
> Project: Ignite
> Issue Type: Bug
> Reporter: Mirza Aliev
> Priority: Major
> Labels: ignite-3
>
> h3. *Motivation*
> After Catalog was introduced and recovery for Distribution zone manager was completed, it is needed to reimplement {{CausalityDataNodesEngine#dataNodes}} according to the new circumstances. Most of the code from this method must be removed, and entities from the catalog must be reused.
> h3. *Definition of done*
> {{CausalityDataNodesEngine#dataNodes}} is reimplemented according to the new circumstances.
> h3. *Implementation notes*
> Seems that we can remove {{CausalityDataNodesEngine#zonesVersionedCfg}} could be removed and Catalog must be used, also we don't need logic for {{CausalityDataNodesEngine#getLastConfigRevision}} because it is guaranteed that immediate scale Up/Down intents will be handled in the corresponding handler
--
This message was sent by Atlassian Jira
(v8.20.10#820010)