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/10/02 08:06:00 UTC
[jira] [Assigned] (IGNITE-13206) Represent in the documenttion
affection of several node addresses on failure detection.
[ https://issues.apache.org/jira/browse/IGNITE-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Steshin reassigned IGNITE-13206:
-----------------------------------------
Assignee: Vladimir Steshin (was: Denis A. Magda)
> Represent in the documenttion affection of several node addresses on failure detection.
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-13206
> URL: https://issues.apache.org/jira/browse/IGNITE-13206
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Major
> Labels: iep-45
> Fix For: 2.9
>
>
> We should emphasize that TcpDiscoverySpi prolongs detection of node failure if several IP addresses are set. Actual failure detection delay is: _failureDetectionTimeout * addressesNumber_.
> "You should assing multiple addresses to a node only if they represent some real physical connections which can give more reliability. Several addresses prolong failure detection of current node. The timeouts and settings on network operations (_failureDetectionTimeout(), sockTimeout, ackTimeout, maxAckTimeout, reconCnt_) work per connection/address. The exception is _connRecoveryTimeout_.
> Example: if you have 3 ip addresses configured for a node, Tcp Discovery takes up to '_failureDetectionTimeout * 3' to detect failure of this node_".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)