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

Posted to issues@ignite.apache.org by "Alexander Belyak (JIRA)" <ji...@apache.org> on 2017/06/08 05:45:18 UTC

[jira] [Updated] (IGNITE-5445) ServerImpl can't process NodeFailedMessage about itself

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

Alexander Belyak updated IGNITE-5445:
-------------------------------------
    Fix Version/s:     (was: 2.1)

> ServerImpl can't process NodeFailedMessage about itself
> -------------------------------------------------------
>
>                 Key: IGNITE-5445
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5445
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: 1.9
>            Reporter: Alexander Belyak
>            Priority: Minor
>
> If for some reason (GC pause or heavy load) node get NodeLeft(FAILED) message about itself - it can't correctly handle it, because it call TcpDiscoveryNodesRing.removeNode with local node id and get assertion error.
> I think - node should correctly determine such event and throw something like "segmented" event and so on.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)