You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Gura (JIRA)" <ji...@apache.org> on 2018/04/18 10:19:00 UTC

[jira] [Updated] (IGNITE-5103) TcpDiscoverySpi ignores maxMissedClientHeartbeats property

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

Andrey Gura updated IGNITE-5103:
--------------------------------
    Fix Version/s:     (was: 2.5)
                   2.6

> TcpDiscoverySpi ignores maxMissedClientHeartbeats property
> ----------------------------------------------------------
>
>                 Key: IGNITE-5103
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5103
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.9
>            Reporter: Valentin Kulichenko
>            Assignee: Dmitry Karachentsev
>            Priority: Major
>             Fix For: 2.6
>
>         Attachments: TcpDiscoveryClientSuspensionSelfTest.java
>
>
> Test scenario is the following:
> * Start one or more servers.
> * Start a client node.
> * Suspend client process using {{-SIGSTOP}} signal.
> * Wait for {{maxMissedClientHeartbeats*heartbeatFrequency}}.
> * Client node is expected to be removed from topology, but server nodes don't do that.
> Attached is the unit test reproducing the same by stopping the heartbeat sender thread on the client.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)