[
https://issues.apache.org/jira/browse/IGNITE-14209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-14209:
-------------------------------------
Epic Name: Data rebalancing
> Data rebalancing
> ----------------
>
> Key: IGNITE-14209
> URL: https://issues.apache.org/jira/browse/IGNITE-14209
> Project: Ignite
> Issue Type: Epic
> Reporter: Vyacheslav Koptilin
> Assignee: Kirill Gusakov
> Priority: Major
> Labels: ignite-3
>
> *Overview*
> The lifecycle of the Ignite cluster assumes that new nodes can join this
> cluster and the old ones can leave it. In order for the data to remain
> distributed equally in the cluster, some replicas have to be moved from one
> Ignite node to another. This process is called data rebalancing.
> The main goal of this umbrella ticket is an approach that can be implemented
> based on Ignite Raft module.
>
> The first implementation phase has the following constraints in order to
> simplify the rebalance process until the table group concept is not defined:
> - only "empty" nodes can join the cluster (in other words, node restart with
> already exists data is not supported)
> - rebalance can be triggered by NODE_JOIN/NODE_FAIL events only in an
> automatic way (alternative option is to introduce IgniteCluster interface
> which allows triggering rebalance in a manual way)
> - reconfiguration of meta-storage nodes is not supported
> Phase 1 includes the following sub-tasks:
> - IGNITE-15125 || IGNITE-15491
> - IGNITE-15490
> - IGNITE-15492
> - IGNITE-15493
> - IGNITE-15288
> - IGNITE-15495
> - IGNITE-15494 (optional)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
