[
https://issues.apache.org/jira/browse/IGNITE-22804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-22804:
---------------------------------------
Description:
When a node is joined to a cluster for the first time, the node gets the
cluster ID from the CMG. The node then saves the cluster ID locally.
We should validate that cluster IDs of the nodes are the same when the nodes
try to establish a network connection: that is, during a handshake, if both
cluster IDs are not empty and are different, we should fail the handshake.
If one of the nodes does not have a cluster ID yet, the validation is skipped.
Having this validation will allow to avoid mixing of the 'new part' of the
cluster (where CMG was recreated) with the 'old part' of the cluster (that was
not available during CMG recreation).
> Refuse network handshake if nodes have different cluster IDs
> ------------------------------------------------------------
>
> Key: IGNITE-22804
> URL: https://issues.apache.org/jira/browse/IGNITE-22804
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> When a node is joined to a cluster for the first time, the node gets the
> cluster ID from the CMG. The node then saves the cluster ID locally.
> We should validate that cluster IDs of the nodes are the same when the nodes
> try to establish a network connection: that is, during a handshake, if both
> cluster IDs are not empty and are different, we should fail the handshake.
> If one of the nodes does not have a cluster ID yet, the validation is skipped.
> Having this validation will allow to avoid mixing of the 'new part' of the
> cluster (where CMG was recreated) with the 'old part' of the cluster (that
> was not available during CMG recreation).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
