[
https://issues.apache.org/jira/browse/IGNITE-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16519630#comment-16519630
]
Dmitriy Pavlov commented on IGNITE-7163:
----------------------------------------
[~sergey-chugunov] [~dkarachentsev] I've found several suspicious tests with 0%
fail rate in master, so I've retriggered these builds.
> Validate connection from a pre-previous node
> --------------------------------------------
>
> Key: IGNITE-7163
> URL: https://issues.apache.org/jira/browse/IGNITE-7163
> Project: Ignite
> Issue Type: Sub-task
> Components: general
> Affects Versions: 2.3
> Reporter: Alexandr Kuramshin
> Assignee: Dmitry Karachentsev
> Priority: Major
> Labels: discovery
> Fix For: 2.6
>
>
> If some pre-previous node connects to the local node with the previous node
> in the message's failed nodes collection additional steps should be done:
> # Connection with the previous node should be validated.
> # If a message from the previous node was not received a long time ago, the
> previous node should be considered as failed and the pre-previous node
> connection accepted.
> # If the previous node connection is alive then different scenarios possible
> ## Answer with a new result code causing the pre-previous node to try to
> reconnect to the previous node
> ## Break connection with the pre-previous node causing to continue the
> possible cluster split.
> ## Check connections with nodes after pre-previous node and delay decision by
> answering RES_WAIT to get more predictable split and stable topology.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
