You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Uttsel (Jira)" <ji...@apache.org> on 2023/05/17 12:50:00 UTC
[jira] [Updated] (IGNITE-19506) Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
[ https://issues.apache.org/jira/browse/IGNITE-19506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Uttsel updated IGNITE-19506:
-----------------------------------
Labels: ignite-3 (was: )
> Use data nodes from DistributionZoneManager with a causality token instead of BaselineManager#nodes
> ---------------------------------------------------------------------------------------------------
>
> Key: IGNITE-19506
> URL: https://issues.apache.org/jira/browse/IGNITE-19506
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Uttsel
> Priority: Major
> Labels: ignite-3
>
> h3. *Motivation*
> Need to use data nodes from DistributionZoneManager instead of BaselineManager#nodes in:
> # DistributionZoneRebalanceEngine#onUpdateReplicas
> # TableManager#createAssignmentsSwitchRebalanceListener
> We need to get data nodes consistently so we need to use revision of configuration events and a meta storage events as causality token. Also need to useĀ
> VersionedValue to save data nodes with causality token.
> h3. *Definition of Done*
> DistributionZoneRebalanceEngine#onUpdateReplicas and TableManager#createAssignmentsSwitchRebalanceListener use data nodes from DistributionZoneManager
--
This message was sent by Atlassian Jira
(v8.20.10#820010)