You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Anton Vinogradov (Jira)" <ji...@apache.org> on 2020/07/03 11:08:00 UTC

[jira] [Resolved] (IGNITE-13205) Represent in logs, javadoc affection of several node addresses on failure detection.

     [ https://issues.apache.org/jira/browse/IGNITE-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton Vinogradov resolved IGNITE-13205.
---------------------------------------
    Resolution: Fixed

> Represent in logs, javadoc affection of several node addresses on failure detection.
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-13205
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13205
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladimir Steshin
>            Assignee: Vladimir Steshin
>            Priority: Minor
>              Labels: iep-45
>             Fix For: 2.9
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Current TcpDiscoverySpi can prolong detection of node failure which has several IP addresses. This happens because most of the timeouts like _failureDetectionTimeout, sockTimeout, ackTimeout_ work per address. Actual failure detection delay is: _failureDetectionTimeout*addressesNumber_ (1). And the node addresses are sorted out consistently. This affection on failure detection should be noted in logs, javadocs.
> *1:  addressesNumber - addresses number of next node in the ring.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)