[
https://issues.apache.org/jira/browse/IGNITE-26572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-26572:
---------------------------------------
Description:
When a node from one cluster tries to connect to a node of another cluster, the
attempt fails and the corresponding message is written to the logs:
node3:e072848a-69b6-4a12-b24d-235b7003cc04 belongs to cluster
7808a96b-18aa-4641-89c2-137d3a6cc6a3 which is different from this one
a032acb2-f2d5-4f26-a80f-a4429c839ab3, connection rejected; should CMG/MG repair
be finished?
It mentions one reason of different cluster IDs.
# It should also mention another reason (that there are 2 clusters that see
each other on the network level)
# It should give the recommendations more prominently
> Improve error message for handshake failure due to wrong cluster ID
> -------------------------------------------------------------------
>
> Key: IGNITE-26572
> URL: https://issues.apache.org/jira/browse/IGNITE-26572
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> When a node from one cluster tries to connect to a node of another cluster,
> the attempt fails and the corresponding message is written to the logs:
> node3:e072848a-69b6-4a12-b24d-235b7003cc04 belongs to cluster
> 7808a96b-18aa-4641-89c2-137d3a6cc6a3 which is different from this one
> a032acb2-f2d5-4f26-a80f-a4429c839ab3, connection rejected; should CMG/MG
> repair be finished?
> It mentions one reason of different cluster IDs.
> # It should also mention another reason (that there are 2 clusters that see
> each other on the network level)
> # It should give the recommendations more prominently
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
