You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/07/27 14:03:00 UTC

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

    [ https://issues.apache.org/jira/browse/IGNITE-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559801#comment-16559801 ] 

ASF GitHub Bot commented on IGNITE-5103:
----------------------------------------

GitHub user ezhuravl opened a pull request:

    https://github.com/apache/ignite/pull/4446

    IGNITE-5103 - Server drops client node from cluster when no metrics u…

    …pdate messages received in clienFailureDetectionTimeout

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-5103

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4446.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4446
    
----
commit 63733ec7ce2875bf92a473534506ee0d354346ba
Author: ezhuravl <ez...@...>
Date:   2018-07-27T13:51:04Z

    IGNITE-5103 - Server drops client node from cluster when no metrics update messages received in clienFailureDetectionTimeout

----


> 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: Evgenii Zhuravlev
>            Priority: Major
>             Fix For: 2.7
>
>         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)