[
https://issues.apache.org/jira/browse/IGNITE-13205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-13205:
--------------------------------------
Description:
Current TcpDiscoverySpi can prolong detection of node failure which has several
IP addresses. This happens because most of the timeouts like
_failureDetectionTimeout, sockTimeout, ackTimeout_ work per address. Actual
failure detection delay is: _failureDetectionTimeout*addressesNumber_ (1). And
the node addresses are sorted out serially. This affection on failure detection
should be noted in logs, javadocs.
*1: addressesNumber - addresses number of next node.
was:Current TcpDiscoverySpi can prolong detection of node failure which has
several IP addresses. This happens because most of the timeouts like
failureDetectionTimeout, sockTimeout, ackTimeout work per address. And the node
addresses are sorted out serially. This affection on failure detection should
be noted in logs, javadocs.
> Represent in logs, javadoc affection of several node addresses on failure
> detection.
> ------------------------------------------------------------------------------------
>
> Key: IGNITE-13205
> URL: https://issues.apache.org/jira/browse/IGNITE-13205
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Major
>
> Current TcpDiscoverySpi can prolong detection of node failure which has
> several IP addresses. This happens because most of the timeouts like
> _failureDetectionTimeout, sockTimeout, ackTimeout_ work per address. Actual
> failure detection delay is: _failureDetectionTimeout*addressesNumber_ (1).
> And the node addresses are sorted out serially. This affection on failure
> detection should be noted in logs, javadocs.
> *1: addressesNumber - addresses number of next node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
