[
https://issues.apache.org/jira/browse/IGNITE-22881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-22881:
---------------------------------------
Reviewer: Mirza Aliev
[~maliev] could you please take a look at the attached PR?
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)