[
https://issues.apache.org/jira/browse/IGNITE-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-13705:
--------------------------------------
Summary: Fix another node failes with failure of target node. (was: Fix
middle node failed when failed next node and previous.)
> Fix another node failes with failure of target node.
> ----------------------------------------------------
>
> Key: IGNITE-13705
> URL: https://issues.apache.org/jira/browse/IGNITE-13705
> Project: Ignite
> Issue Type: Bug
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The discovery ducktape test [1] has detected failure of third node in the
> middle of 2 simulateously failed nodes.
> Scenario:
> Two nodes fail at the same time. The nodes have relative places in the ring:
> N-1 and N+1.
> Node N detects failure of node N+1. Node N tries to connect to node N+2. Node
> N+2 checks backward connection to node N+1.
> Problem:
> Node N can fail too.
> Cause:
> The timeout on node N to recover connection to node N+2 appears shorter than
> timeout on node N+2 to check connection to N+1.
> Fix:
> Introduced a fundamental timeout value to check/recover connection based on
> current configuration. Not a constant. Mentioned above timeouts have been
> made relative. The timeout of backward connection check is now generally
> shorter than the timeout to recover connection.
> [1]
> https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
