[
https://issues.apache.org/jira/browse/IGNITE-19061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev resolved IGNITE-19061.
----------------------------------
Fix Version/s: 3.0.0-beta2
Resolution: Done
> Node restart rewrites data nodes with too actual nodes (Design ticket)
> ----------------------------------------------------------------------
>
> Key: IGNITE-19061
> URL: https://issues.apache.org/jira/browse/IGNITE-19061
> Project: Ignite
> Issue Type: Bug
> Reporter: Mirza Aliev
> Assignee: Mirza Aliev
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, in the {{DistributionZoneManager.start}} method we have a logic
> that initialises data nodes in Meta Storage. It takes logical topology from
> Vault and write it to the Meta Storage as a data nodes.
> This behaviour is not correct, lets consider the scenario:
> # We have cluster [A, B, C], new node E was added to the logical topology,
> scale up timer was scheduled to add that node to a data nodes of some zone
> Zone_1 after 1 hour.
> # Right after that node A from cluster was restarted, so it will rewrite data
> nodes for Zone_1 according the logic from the
> {{DistributionZoneManager.start}}
> # Data nodes of Zone_1 become [A, B, C, E], but user was expecting, that data
> nodes for Zone_1 will be changed after 1 hour.
> UPD:
> Current ticket is reclassified to the ticket for design, so the proper
> solution for the restart and restoring timers must be provided.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
