[
https://issues.apache.org/jira/browse/IGNITE-18115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-18115:
-------------------------------------
Description:
h3. Motivation
As was mentioned in https://issues.apache.org/jira/browse/IGNITE-18087 In order
to calculate dataNodes for each distribution zone it's required to have proper
actor that will listen to:
* Logical topology events.
* Distribution zone reconfiguration events (adding, updating, removing).
* Distribution zone processing enabling/disabling.
and properly react to such events. As you can see from IGNITE-18087 we have two
phase reaction on logical topology events. During the first phase we update
logicalTopology and logicalTopologyVersion inside meta storage and don't
trigger dataNodes recalculation directly. Why? Because it's simpler - after
inserting
> Populate DistributionZoneManager with MetaStorage listeners to logical
> topology events
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-18115
> URL: https://issues.apache.org/jira/browse/IGNITE-18115
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexander Lapin
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> As was mentioned in https://issues.apache.org/jira/browse/IGNITE-18087 In
> order to calculate dataNodes for each distribution zone it's required to have
> proper actor that will listen to:
> * Logical topology events.
> * Distribution zone reconfiguration events (adding, updating, removing).
> * Distribution zone processing enabling/disabling.
> and properly react to such events. As you can see from IGNITE-18087 we have
> two phase reaction on logical topology events. During the first phase we
> update logicalTopology and logicalTopologyVersion inside meta storage and
> don't trigger dataNodes recalculation directly. Why? Because it's simpler -
> after inserting
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
