[
https://issues.apache.org/jira/browse/IGNITE-19288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Uttsel updated IGNITE-19288:
-----------------------------------
Description:
h3. Motivation
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
h3. Definition of Done
* Concurrency bug is fixed.
* Test is enabled.
was:
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
> 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
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> 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
> h3. Definition of Done
> * Concurrency bug is fixed.
> * Test is enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
