You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/03 10:03:05 UTC
[jira] [Updated] (IGNITE-8356) Possible race at the discovery on
the start node
[ https://issues.apache.org/jira/browse/IGNITE-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-8356:
------------------------------------
Fix Version/s: (was: 2.8)
2.9
> Possible race at the discovery on the start node
> ------------------------------------------------
>
> Key: IGNITE-8356
> URL: https://issues.apache.org/jira/browse/IGNITE-8356
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Taras Ledkov
> Priority: Major
> Fix For: 2.9
>
>
> The problem was discovered on the IGNITE-8355.
> But *root cause* is the race on the start of the node discovery.
> The race happens because a joining node may start processing NodeAddMessage before processing local node's NodeAddFinishedMessage. Because of this, the local node will not have any constructed DiscoCache yet and NPE happens.
> We need to take a look at the workaround suggested in IGNITE-8355 and
> 1) Check if any public API changes are needed on DiscoverySpi interface
> 2) Verify it works for ZookeeperDiscoverySpi.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)