[
https://issues.apache.org/jira/browse/IGNITE-19424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov updated IGNITE-19424:
------------------------------------
Description:
The heart of the new [rebalance
mechanism|https://github.com/apache/ignite-3/blob/c276a334c4c3742520494bccdc957f4530c8ed7a/modules/distribution-zones/tech-notes/rebalance.md]
is the fact, that all data storages and replicas groups will be builded around
the distribution zone partitions, but not around the table partitions.
But at the current moment datastorage management is still table-based. To the
unlock activities of the rebalance track the following workaround was
introduced: support only rebalance of the zones, which have strictly 1 table
and remove this restrictions, when
> Fix rebalance logic after implementation a zone aware data collocation
> ----------------------------------------------------------------------
>
> Key: IGNITE-19424
> URL: https://issues.apache.org/jira/browse/IGNITE-19424
> Project: Ignite
> Issue Type: Task
> Reporter: Kirill Gusakov
> Priority: Major
>
> The heart of the new [rebalance
> mechanism|https://github.com/apache/ignite-3/blob/c276a334c4c3742520494bccdc957f4530c8ed7a/modules/distribution-zones/tech-notes/rebalance.md]
> is the fact, that all data storages and replicas groups will be builded
> around the distribution zone partitions, but not around the table partitions.
> But at the current moment datastorage management is still table-based. To the
> unlock activities of the rebalance track the following workaround was
> introduced: support only rebalance of the zones, which have strictly 1 table
> and remove this restrictions, when
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
