[
https://issues.apache.org/jira/browse/IGNITE-19440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-19440:
-------------------------------------
Description:
h3. Motivation
While reviewing https://issues.apache.org/jira/browse/IGNITE-18955 it became
obvious that having zone specific details in TableManager in particular ones
that are exposed through distributionZonesDataNodesListener and partial
dataNodes emptiness check is a result of bad design and should be fixed ASAP.
The core idea here is that instead of TableManager Distribution Zones should
manage rebalance logic and moving
was:
h3. Motivation
While reviewing https://issues.apache.org/jira/browse/IGNITE-18955 it became
obvious that having zone specific details in TableManager in particular ones
that are exposed throughÂ
> Move onUpdateReplicas and distributionZonesDataNodesListener from table
> manager to distribution zones
> -----------------------------------------------------------------------------------------------------
>
> Key: IGNITE-19440
> URL: https://issues.apache.org/jira/browse/IGNITE-19440
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Motivation
> While reviewing https://issues.apache.org/jira/browse/IGNITE-18955 it became
> obvious that having zone specific details in TableManager in particular ones
> that are exposed through distributionZonesDataNodesListener and partial
> dataNodes emptiness check is a result of bad design and should be fixed ASAP.
> The core idea here is that instead of TableManager Distribution Zones should
> manage rebalance logic and moving
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
