[
https://issues.apache.org/jira/browse/IGNITE-20310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Uttsel updated IGNITE-20310:
-----------------------------------
Description:
There are meta storage invokes in DistributionZoneManager start. Currently it
does the meta storage invokes in
DistributionZoneManager#createOrRestoreZoneState:
# DistributionZoneManager#initDataNodesAndTriggerKeysInMetaStorage to update
data nodes.
# DistributionZoneManager#restoreTimers. in case when a filter update was
handled before DZM stop, but it didn't update data nodes.
Futures of these invokes are ignored. So after the start method is completed
actually not all start actions are completed.
was:
There are meta storage invokes in DistributionZoneManager start. Currently it
does the meta storage invoke in case when a filter update was handled before
DZM stop, but it didn't update data nodes. The future of this invoke is
ignored. So after the start method is completed actually not all start actions
are completed.
> Meta storage invokes are not completed when DZM start is completed
> -------------------------------------------------------------------
>
> Key: IGNITE-20310
> URL: https://issues.apache.org/jira/browse/IGNITE-20310
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Uttsel
> Priority: Major
> Labels: ignite-3
>
> There are meta storage invokes in DistributionZoneManager start. Currently it
> does the meta storage invokes in
> DistributionZoneManager#createOrRestoreZoneState:
> # DistributionZoneManager#initDataNodesAndTriggerKeysInMetaStorage to update
> data nodes.
> # DistributionZoneManager#restoreTimers. in case when a filter update was
> handled before DZM stop, but it didn't update data nodes.
> Futures of these invokes are ignored. So after the start method is completed
> actually not all start actions are completed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
