[
https://issues.apache.org/jira/browse/IGNITE-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-13663:
--------------------------------------
Description:
We should emphasize that TcpDiscoverySpi prolongs detection of node failure if
several IP addresses are set. Actual failure detection delay is:
failureDetectionTimeout * addressesNumber + connRecoveryTimeout.
The problem is node can have many addresses to connect to. 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.
was:
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. If no address set,
all available IP addresses are automaticall picked up. Several addresses
prolong failure detection of current node. The timeouts and settings on network
operations (failureDetectionTimeout(), sockTimeout, ackTimeout, maxAckTimeout,
reconCnt) work per 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".
> 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: Vladimir Steshin
> 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 + connRecoveryTimeout.
> The problem is node can have many addresses to connect to. 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)
