[IGNITE-13206] Represent in the documenttion affection of several node addresses on failure detection.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Later
• Fix Version/s: 2.10
• Component/s: documentation
• Labels: iep-45
• Ignite Flags: Docs Required
• Assignee: Vladimir Steshin
• Reporter: Vladimir Steshin
• Created: 02/Jul/20 12:46
• Updated: 11/Nov/20 11:37
• Resolved: 03/Nov/20 14:02

Description

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".

Issue Links

• causes: IGNITE-13663 Represent in the documenttion affection of several node addresses on failure detection v2.
• is caused by: IGNITE-13012 Fix failure detection timeout. Simplify node ping routine.
• is part of: IGNITE-13205 Represent in logs, javadoc affection of several node addresses on failure detection.
• links to: GitHub Pull Request #8312