[
https://issues.apache.org/jira/browse/IGNITE-19736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-19736:
---------------------------------
Epic Link: IGNITE-19743 (was: IGNITE-19577)
> Do not cancel tasks in DistributionZoneManager#executor if they were created
> by immediate scaleUp/scaleDown events.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-19736
> URL: https://issues.apache.org/jira/browse/IGNITE-19736
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Uttsel
> Assignee: Sergey Uttsel
> Priority: Major
> Labels: ignite-3
>
> h3. *Motivation*
> When topology is changed it triggers scheduling a task in the executor to
> update data nodes. If there is another not started task in the queue then an
> old task will be canceled. So even if scaleUp/scaleDown timers are immediate
> it is possible that some topology change will be skipped because the task
> will be canceled.
> We need do not cancel tasks in an executor if the task was triggered by
> immediate data nodes calculation.
> h3. *Definition of Done*
> # Do not cancel tasks in an executor if the task was triggered by immediate
> data nodes calculation.
> # All data nodes calculation tasks must be executed in order of creation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
