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 2017/09/08 10:24:00 UTC

[jira] [Commented] (IGNITE-5718) Forcible node drop makes cluster instable in some cases.

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

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

Github user AMashenkov closed the pull request at:

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


> Forcible node drop makes cluster instable in some cases.
> --------------------------------------------------------
>
>                 Key: IGNITE-5718
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5718
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 2.0
>            Reporter: Andrew Mashenkov
>            Assignee: Andrew Mashenkov
>             Fix For: 2.3
>
>
> Communication SPI can drop nodes from topology due to short network issues regardless failureDetectionTimout.
> Also, we throw IgniteCheckedExcpetion in safeHandshake method without any retry
> if remote node close connection (possibly by timeout) due to short network issues. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)