[
https://issues.apache.org/jira/browse/IGNITE-19581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev updated IGNITE-19581:
---------------------------------
Description:
In https://issues.apache.org/jira/browse/IGNITE-19061 we have provided design
for a correct restart of a node and recovering all Distributed Zones states.
In this ticket we want to take into account immediate scale up when filter was
changed, so this intent must be restored after restart. In the ticket
https://issues.apache.org/jira/browse/IGNITE-19580 we restored all zones'
states, including all scheduled before restart timers, but node could be
restarted when immediate scale up was running, so data nodes weren't updated
before restart. This immediate propagation must be done while node is
restarting.
Details could be found in the design document
was:
In https://issues.apache.org/jira/browse/IGNITE-19061 we have provided design
for a correct restart of a node and recovering all Distributed Zones states.
In this ticket we want to take into account immediate scale up when filter was
changed, so this intent must be restored after restart.
Details could be found in the design document
> Implement restoring of immediate scale up intent after restart when a filter
> was changed
> ----------------------------------------------------------------------------------------
>
> Key: IGNITE-19581
> URL: https://issues.apache.org/jira/browse/IGNITE-19581
> Project: Ignite
> Issue Type: Bug
> Reporter: Mirza Aliev
> Priority: Major
> Labels: ignite-3
>
> In https://issues.apache.org/jira/browse/IGNITE-19061 we have provided design
> for a correct restart of a node and recovering all Distributed Zones states.
> In this ticket we want to take into account immediate scale up when filter
> was changed, so this intent must be restored after restart. In the ticket
> https://issues.apache.org/jira/browse/IGNITE-19580 we restored all zones'
> states, including all scheduled before restart timers, but node could be
> restarted when immediate scale up was running, so data nodes weren't updated
> before restart. This immediate propagation must be done while node is
> restarting.
> Details could be found in the design document
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
