[ https://issues.apache.org/jira/browse/IGNITE-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763589#comment-16763589 ]
Sergey Chugunov commented on IGNITE-10926: ------------------------------------------ [~NSAmelchev], I reviewed patch one more time, it looks good to me as client node now fires RECONNECT event only after a successful join. I suggest to remove {{Ignore}} annotation from tests {{testReconnectServersRestart_1}} and {{testReconnectServersRestart_2}} as they should be fixed by this change. If so we may even close related ticket IGNITE-8178. Thank you for your contribution! > 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)