You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2024/09/01 14:04:00 UTC
[jira] [Assigned] (IGNITE-22881) Handle logical topology event version reset in DistributionZoneManager
[ https://issues.apache.org/jira/browse/IGNITE-22881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Puchkovskiy reassigned IGNITE-22881:
------------------------------------------
Assignee: Roman Puchkovskiy
> Handle logical topology event version reset in DistributionZoneManager
> ----------------------------------------------------------------------
>
> Key: IGNITE-22881
> URL: https://issues.apache.org/jira/browse/IGNITE-22881
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: iep-128, ignite-3
>
> DistributionZoneManager listens to logical topology events and writes new logical topology versions to the Metastorage. It relies on monotinicity of logical topology events' versions. When CMG is reset, version number is reset to 1, breaking monotonicity.
> One way to solve the problem is to pass current cluster ID to the event handler, so it can distinguish between 'same version=1 created by other node' and 'different version=1 exists remaining from the old cluster ID'.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)