[
https://issues.apache.org/jira/browse/IGNITE-22808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-22808:
---------------------------------------
Description:
A method in a manager used for CMG disaster recovery (see IGNITE-22876) should
be added:
CompletableFuture<Void> migrate(ClusterState newClusterState)
It should do the following:
# Create a ClusterResetMessage from newClusterState
# Send this message to every node in the physical topology (including itself)
# After getting a response, or exception due to node leaving topology, or a
timeout from each node, restart the node
was:
A method in a manager used for CMG disaster recovery (see IGNITE-22876) should
be added:
CompletableFuture<Void> migrate(ClusterState newClusterState)
It should do the following:
# Create a ClusterResetMessage from newClusterState
# Send this message to every node in the physical topology (including itself)
# It should then act (wrt waiting and restarting itself) in the same vein as
in IGNITE-22876
> Migrate running node missed during CMG reparation to new cluster
> ----------------------------------------------------------------
>
> Key: IGNITE-22808
> URL: https://issues.apache.org/jira/browse/IGNITE-22808
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A method in a manager used for CMG disaster recovery (see IGNITE-22876)
> should be added:
> CompletableFuture<Void> migrate(ClusterState newClusterState)
> It should do the following:
> # Create a ClusterResetMessage from newClusterState
> # Send this message to every node in the physical topology (including itself)
> # After getting a response, or exception due to node leaving topology, or a
> timeout from each node, restart the node
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
