You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Steshin (Jira)" <ji...@apache.org> on 2020/11/03 16:47:00 UTC

[jira] [Assigned] (IGNITE-13663) Represent in the documenttion affection of several node addresses on failure detection v2.

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

Vladimir Steshin reassigned IGNITE-13663:
-----------------------------------------

    Assignee: Denis A. Magda  (was: Vladimir Steshin)

> Represent in the documenttion affection of several node addresses on failure detection v2.
> ------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-13663
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13663
>             Project: Ignite
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.9
>            Reporter: Vladimir Steshin
>            Assignee: Denis A. Magda
>            Priority: Major
>              Labels: iep-45
>             Fix For: 2.10
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We should emphasize in the documentation that TcpDiscoverySpi prolongs detection of node failure if several IP addresses are set. Actual failure detection delay is: failureDetectionTimeout * addressesNumber + connRecoveryTimeout.
> The problem is ability of node to run on several addresses. By default, all non-loop back addresses are assigned to node. Connection to a node is
> established to one of its address. But if lost, other addresses are attempted to reconnect to sequentially.



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