You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2020/12/02 08:54:00 UTC

[jira] [Commented] (IGNITE-13705) Another node fails with failure of target node.

    [ https://issues.apache.org/jira/browse/IGNITE-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242177#comment-17242177 ] 

Ignite TC Bot commented on IGNITE-13705:
----------------------------------------

{panel:title=Branch: [pull/8484/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8484/head] Base: [master] : New Tests (2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}SPI{color} [[tests 2|https://ci.ignite.apache.org/viewLog.html?buildId=5768007]]
* {color:#013220}IgniteSpiTestSuite: TcpDiscoveryNetworkIssuesTest.testNotSequentialFailTwoNodes - PASSED{color}
* {color:#013220}IgniteSpiTestSuite: TcpDiscoveryNetworkIssuesTest.testSequentialFailTwoNodes - PASSED{color}

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5768095&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Another node fails 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: 1h 40m
>  Remaining Estimate: 0h
>
> The discovery ducktape test [1] has detected unexpected failure of another node.
> Scenario:
> The nodes have relative places in the ring: N 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. The mentioned timeouts have been turned 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)