You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Sergey Chugunov (Jira)" <ji...@apache.org> on 2026/01/28 12:43:00 UTC

[jira] [Updated] (IGNITE-25700) Fix flaky test TcpDiscoverySpiFailureTimeoutSelfTest#testConnectionCheckMessage

     [ https://issues.apache.org/jira/browse/IGNITE-25700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Chugunov updated IGNITE-25700:
-------------------------------------
    Epic Link: IGNITE-27674

> Fix flaky test TcpDiscoverySpiFailureTimeoutSelfTest#testConnectionCheckMessage
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-25700
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25700
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Maksim Timonin
>            Assignee: Maksim Timonin
>            Priority: Major
>              Labels: IEP-132, ise
>             Fix For: 2.18
>
>
> Test TcpDiscoverySpiFailureTimeoutSelfTest#testConnectionCheckMessage sometimes fails. The test awaits 15-25 TcpDiscoveryConnectionCheckMessage during failure detection timeout (10000ms). But sometimes test fails because there are only 14 messages.
> TcpDiscoveryConnectionCheckMessage is sent by timeout (500ms) if no other messages were sent in the period. The test expects if no activity on the cluster then ~20 msgs should be sent. But actually there is TcpDiscoveryMetricsUpdateMessage is sent every 2000ms.
> Within the failure detection period it can be sent 6 times, and then reset the timer 6 times. In corner case (20 - 6 = 14) msgs of the check message will be sent.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)