[
https://issues.apache.org/jira/browse/IGNITE-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Steshin updated IGNITE-13206:
--------------------------------------
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 the documentation.
*1: addressesNumber - addresses number of next node in the ring.
Summary: Represent in the documenttion affection of several node
addresses on failure detection. (was: Represent in the doc affection of
several node addresses on failure detection.)
> Represent in the documenttion affection of several node addresses on failure
> detection.
> ---------------------------------------------------------------------------------------
>
> Key: IGNITE-13206
> URL: https://issues.apache.org/jira/browse/IGNITE-13206
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Minor
>
> 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 the documentation.
> *1: addressesNumber - addresses number of next node in the ring.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
