You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2017/07/12 06:02:00 UTC

[jira] [Resolved] (IGNITE-5727) Node failed listener for TcpCommunicationSpi should be called first

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

Semen Boikov resolved IGNITE-5727.
----------------------------------
    Resolution: Fixed
      Assignee:     (was: Semen Boikov)

Fixed in master (b95f76f8a0a3a7e920f78f20b3d814112fc6d522).

> Node failed listener for TcpCommunicationSpi should be called first
> -------------------------------------------------------------------
>
>                 Key: IGNITE-5727
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5727
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>            Reporter: Semen Boikov
>            Priority: Critical
>             Fix For: 2.2
>
>
> Ignite components rely on assumption that if node failed then it is not possible to send message to this node (TcpCommunicationSpi.send should throw an exception). If it was possible to send event and after this node failed, then components' node_left listener will be called. But actually this will work only if component's node_left listener is called after TcpCommunicationSpi's listener. Need change node_left listener's order so that  TcpCommunicationSpi's listener is always called first.



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