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

Posted to issues@ignite.apache.org by "Vladimir Steshin (Jira)" <ji...@apache.org> on 2020/05/27 11:02:00 UTC

[jira] [Resolved] (IGNITE-13018) Get rid of duplicated checking of failed node.

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

Vladimir Steshin resolved IGNITE-13018.
---------------------------------------
    Resolution: Duplicate

Duplicates IGNITE-13014.

> Get rid of duplicated checking of failed node.
> ----------------------------------------------
>
>                 Key: IGNITE-13018
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13018
>             Project: Ignite
>          Issue Type: Sub-task
>            Reporter: Vladimir Steshin
>            Assignee: Vladimir Steshin
>            Priority: Major
>              Labels: iep-45
>
> Failed node checking should be simplified to one step: ping node (send a message) from previous one in the ring and wait for response within IgniteConfiguration.failureDetectionTimeout. If node doesn't respond, we should consider it failed. Extra steps of connection checking may seriously delay failure detection, bring confusion and weird behavior.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)