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/08 13:44:00 UTC
[jira] [Commented] (IGNITE-10417) notifyDiscoveryListener() call
can be lost.
[ https://issues.apache.org/jira/browse/IGNITE-10417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16946890#comment-16946890 ]
Maxim Muzafarov commented on IGNITE-10417:
------------------------------------------
[~voropava][~dmekhanikov]
Folks, any update on this issue?
> notifyDiscoveryListener() call can be lost.
> -------------------------------------------
>
> Key: IGNITE-10417
> URL: https://issues.apache.org/jira/browse/IGNITE-10417
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Pavel Voronkin
> Assignee: Pavel Voronkin
> Priority: Major
> Fix For: 2.8
>
>
> 1) ServerImpl:5455 notifyDiscoveryListener can not be called in case of spiState != CONNECTED, for example DISCONNECTING which is valid state nevetheless inside notifyDiscoveryListener we check spiState == CONNECTED || spiState == DISCONNECTING, also we need to improve logging in notifyDiscoveryListener().
> 2) Improve logging on duplicated custom discovery event.
> 3) Add assert if msg.creatorNodeId() doesn't exist in topology this is bad behaviour taht should lead to node fail.
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)