[jira] [Commented] (IGNITE-10926) ZookeeperDiscoverySpi: client does not survive after several cluster restarts

["Amelchev Nikita (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758079#comment-16758079 ] 

Amelchev Nikita commented on IGNITE-10926:
------------------------------------------

I have fixed PR. Now reconnect event will fire if the client node was connected to a previous topology.

Also, I have found that flaky authentication test was broken and correct my changes. 
Before failing local node I check on join errors. And for minor optimization, I moved the initialization of the client node watcher to the join error watcher that starts after a timeout. 

[~sergey-chugunov], Could you take a look at the changes one more time, please? 

> 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)