[
https://issues.apache.org/jira/browse/IGNITE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756156#comment-16756156
]
Amelchev Nikita commented on IGNITE-10926:
------------------------------------------
[~agoncharuk] No, the order of these events will not be changed.
The difference is only for the case when client join request wasn't handled
between cluster restarts. (Wasn't be joined to topology in previous connect
retry)
In the master: after several cluster restart the client join will fire only the
{{NODE_JOINED}} event and will not fire the {{RECONNECTED}} event.
In the fix: after several cluster restart the client join will fire the
{{NODE_JOINED}} and the {{RECONNECTED}} events.
> ZookeeperDiscoverySpi: client does not survive after several cluster restarts
> -----------------------------------------------------------------------------
>
> Key: IGNITE-10926
> URL: https://issues.apache.org/jira/browse/IGNITE-10926
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
> Reporter: Amelchev Nikita
> Assignee: Amelchev Nikita
> Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{ZookeeperDiscoveryImpl#cleanupPreviousClusterData}} can delete alive node
> of a client in case of low internal order.
> Steps to reproduce:
> 1. Start server and client.
> 2. Stop the server and wait for the client disconnected.
> 3. Start and stop the server. The server hasn't time to process client join
> request.
> 4. Start server. It will delete alive client node because the client has low
> internal order. The client will never connect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
