[
https://issues.apache.org/jira/browse/IGNITE-13134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148574#comment-17148574
]
Vladimir Steshin commented on IGNITE-13134:
-------------------------------------------
The patch creates
{code:java}
JmhNodeFailureDetection
{code}
and
{code:java}
TcpDiscoveryNetworkIssuesTest.testConnectionRecoveryTimeoutSmallValues()
TcpDiscoveryNetworkIssuesTest.testConnectionRecoveryTimeoutMediumValues()
TcpDiscoveryNetworkIssuesTest.testConnectionRecoveryTimeoutLongValues()
{code}
The benchmark shows delay on node segmentation. Expected:
failureDetectionTimeout + connRecoveryTimeout.
You can find in the output (example):
Master: Detection delay: *1923*. Failure detection timeout: 1000, connection
recovery timeout: 500
Fixed: Detection delay: 1408. Failure detection timeout: 1000, connection
recovery timeout: 500
> Fix connection recovery timout.
> -------------------------------
>
> Key: IGNITE-13134
> URL: https://issues.apache.org/jira/browse/IGNITE-13134
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.8.1
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Major
> Labels: iep-45
> Attachments: IGNITE-130134-patch.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If node experiences connection issues it must establish new connection or
> fail within failureDetectionTimeout + connectionRecoveryTimout.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
