[
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 document that TcpDiscoverySpi prolongs detection of node failure if
node has several addresses.
By default, all available addresses are assigned to node and node listens any
address (0.0.0.0). Not first non-loopback addresses as the documentation says.
Actual failure detection delay of this node is: `failureDetectionTimeout *
addressesNumber + connRecoveryTimeout`. Which is usually unexpectable.
To avoid this, user should assign `IgniteConfiguration.localHost` or
`TcpDiscoverySpi.localAddress`.
Often, middleware runs in environments with several IP addresses
(virtualizations, containers, different networks). Node sends all obtained
addresses with other node info to the cluster. Connection to node is
established to first of its addresses. But if lost, other addresses are
attempted to reconnect sequentially. If addresses do not belong to assumed node
network, do not represent existing physical connection, processing them is just
waste of time. However, users frequently skip this setting and allow node to
activate all available IPs
was:
We should document that TcpDiscoverySpi prolongs detection of node failure if
node has several addresses. By default, all available addresses are assigned to
node and node listens any address (0.0.0.0). Actual failure detection delay of
this node is: `failureDetectionTimeout * addressesNumber +
connRecoveryTimeout`.
To avoid this, user should assign `IgniteConfiguration.localHost` or
`TcpDiscoverySpi.localAddress`.
Often, middleware runs in environments with several IP addresses
(virtualizations, containers, different networks). Node sends all obtained
addresses with other node info to the cluster. Connection to node is
established to first of its addresses. But if lost, other addresses are
attempted to reconnect sequentially. If addresses do not belong to assumed node
network, do not represent existing physical connection, processing them is just
waste of time.
> 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.7.6, 2.9, 2.8.1
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Major
> Labels: iep-45
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We should document that TcpDiscoverySpi prolongs detection of node failure if
> node has several addresses.
> By default, all available addresses are assigned to node and node listens any
> address (0.0.0.0). Not first non-loopback addresses as the documentation
> says. Actual failure detection delay of this node is:
> `failureDetectionTimeout * addressesNumber + connRecoveryTimeout`. Which is
> usually unexpectable.
> To avoid this, user should assign `IgniteConfiguration.localHost` or
> `TcpDiscoverySpi.localAddress`.
> Often, middleware runs in environments with several IP addresses
> (virtualizations, containers, different networks). Node sends all obtained
> addresses with other node info to the cluster. Connection to node is
> established to first of its addresses. But if lost, other addresses are
> attempted to reconnect sequentially. If addresses do not belong to assumed
> node network, do not represent existing physical connection, processing them
> is just waste of time. However, users frequently skip this setting and allow
> node to activate all available IPs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
