You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2023/02/03 11:53:00 UTC
[jira] [Updated] (IGNITE-18088) Trigger rebalance on zone.dataNodes change
[ https://issues.apache.org/jira/browse/IGNITE-18088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Lapin updated IGNITE-18088:
-------------------------------------
Fix Version/s: 3.0.0-beta2
> Trigger rebalance on zone.dataNodes change
> ------------------------------------------
>
> Key: IGNITE-18088
> URL: https://issues.apache.org/jira/browse/IGNITE-18088
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Assignee: Sergey Uttsel
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 6h 20m
> Remaining Estimate: 0h
>
> h3. Motivation
> Core idea is to rebalance table data after some topology events. Distribution zones both provide corresponding triggers and set of nodes to perform affinity recalculation, meaning that dataNodes _change_ is a trigger and dataNode _state_ is an input for an affinity recalculation. Thus it's required for partition to listen for such events though ms watches and call old-fashioned rebalance logic.
> *Definition of Done*
> Rebalance is performed after dataNodes changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)