You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Sergey Uttsel (Jira)" <ji...@apache.org> on 2023/04/14 13:31:00 UTC

[jira] [Created] (IGNITE-19288) A race on scheduling data nodes updates if there new nodes and stopped nodes in logical topology

Sergey Uttsel created IGNITE-19288:
--------------------------------------

             Summary: A race on scheduling data nodes updates if there new nodes and stopped nodes in logical topology
                 Key: IGNITE-19288
                 URL: https://issues.apache.org/jira/browse/IGNITE-19288
             Project: Ignite
          Issue Type: Bug
            Reporter: Sergey Uttsel
            Assignee: Mirza Aliev


If new logical topology has a new nodes and nodes that left cluster then DistributionZoneManager#scheduleTimers() schedules saveDataNodesOnScaleUp and  saveDataNodesOnScaleDown. These tasks are invoked asynchronously but use the same entry in topologyAugmentationMap. So scale up puts entry with some revision and then scale down puts entry with the same revision as key.
The issue is reproduced by DistributionZoneAwaitDataNodesTest#testSeveralScaleUpAndSeveralScaleDownThenScaleUpAndScaleDown



--
This message was sent by Atlassian Jira
(v8.20.10#820010)