[
https://issues.apache.org/jira/browse/IGNITE-22807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-22807:
---------------------------------------
Description:
If, during an Ignite node startup, it finds a ClusterResetMessage stored in its
Vault, it does the following (before starting the networking):
# Assign cluster ID from the message instead of the cluster ID stored in the
local CMG data for the network handshake validation
# Start the network
# If the cluster ID stored in the local CMG data is different from the one
from the message, then:
## Destroys the local CMG data and CMG Raft storages (meta, snapshots, log)
## Initializes a new CMG Raft node using the new CMG nodes (from the message)
as voting set
## Submits a CmgInitCommand (having new CMG nodes, MG nodes from old CMG, new
cluster name and tag, new cluster ID history) to the new CMG
> Repair CMG on node start
> ------------------------
>
> Key: IGNITE-22807
> URL: https://issues.apache.org/jira/browse/IGNITE-22807
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> If, during an Ignite node startup, it finds a ClusterResetMessage stored in
> its Vault, it does the following (before starting the networking):
> # Assign cluster ID from the message instead of the cluster ID stored in the
> local CMG data for the network handshake validation
> # Start the network
> # If the cluster ID stored in the local CMG data is different from the one
> from the message, then:
> ## Destroys the local CMG data and CMG Raft storages (meta, snapshots, log)
> ## Initializes a new CMG Raft node using the new CMG nodes (from the
> message) as voting set
> ## Submits a CmgInitCommand (having new CMG nodes, MG nodes from old CMG,
> new cluster name and tag, new cluster ID history) to the new CMG
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
