This is an automated email from the ASF dual-hosted git repository.

dmagda pushed a commit to branch IGNITE-7595
in repository https://gitbox.apache.org/repos/asf/ignite.git


The following commit(s) were added to refs/heads/IGNITE-7595 by this push:
     new 8b5980d  First impl. (#8312)
8b5980d is described below

commit 8b5980d60f2d9b152f196ce51aae274b42297c6f
Author: Vladsz83 <vlads...@gmail.com>
AuthorDate: Mon Oct 5 23:20:05 2020 +0300

    First impl. (#8312)
---
 docs/_docs/clustering/tcp-ip-discovery.adoc | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/_docs/clustering/tcp-ip-discovery.adoc 
b/docs/_docs/clustering/tcp-ip-discovery.adoc
index 30c8727..16249ef 100644
--- a/docs/_docs/clustering/tcp-ip-discovery.adoc
+++ b/docs/_docs/clustering/tcp-ip-discovery.adoc
@@ -7,6 +7,15 @@ Ignite provides `TcpDiscoverySpi` as a default implementation 
of `DiscoverySpi`
 Discovery SPI can be configured for Multicast and Static IP based node
 discovery.
 
+[NOTE]
+====
+[discrete]
+You should configure multiple node addresses only if they represent some real 
connections which can give you more
+reliability. Setting several addresses may prolong detection of node failure. 
Parameters like `failureDetectionTimeout`
+work per address sequentially. If you assign, for example, two ip addresses a 
node, TcpDiscovery takes up to
+'failureDetectionTimeout * 2' to detect failure of this node.
+====
+
 == Multicast IP Finder
 
 `TcpDiscoveryMulticastIpFinder` uses Multicast to discover other nodes

Reply via email to