ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Voronkin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-10417) notifyDiscoveryListener() call can be lost
Date Tue, 27 Nov 2018 11:55:00 GMT

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

Pavel Voronkin updated IGNITE-10417:
------------------------------------
    Description: 
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.

 

 

 

 

 

  was:
1) ServerImpl: 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 event.

3) Add assert if msg.creatorNodeId() doesn't exist in topology this is bad behaviour taht
should lead to node fail.

 

 

 

 

 


> notifyDiscoveryListener() call can be lost
> ------------------------------------------
>
>                 Key: IGNITE-10417
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10417
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Pavel Voronkin
>            Assignee: Pavel Voronkin
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message