[
https://issues.apache.org/jira/browse/IGNITE-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17208299#comment-17208299
]
Denis A. Magda commented on IGNITE-13206:
-----------------------------------------
[~vladsz83], I've merged your pull-request and only then realized that the
description explains the communication and not the discovery SPI.
If I'm not mistaken, the addresses that you set in the discovery configuration
are used during the node join-process and multiple unreachable addresses can
prolong the node's startup time. Once, the node connects it will receive IPs of
all alive nodes and will use those for the peer-to-peer communication. Thus,
I've changed the callout and made it sound the discovery-specific
[WARNING]
====
[discrete]
Provide multiple node addresses only if you are sure that those are reachable.
The unreachable addresses increase the
time it takes for the nodes to join the cluster. Let's say you set five IP
addresses, and nobody listens for incoming
connections on two addresses out of five. If Ignite starts connecting to the
cluster via those two unreachable addresses,
it will impact the node's startup time.
====
As for your contribution that explains the things related to the
failureDetectionTimeout and communication spi, should we put it under the
communication spi section?
Btw, I'm merging the IGNITE-7595 branch to the master today. So, if you decide
to send another pull-request, target the master please.
> 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: Denis A. Magda
> Priority: Major
> Labels: iep-45
> Fix For: 2.10
>
>
> 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 + connRecoveryTimeout' to detect
> failure of this node_".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
