[ https://issues.apache.org/jira/browse/IGNITE-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510835#comment-16510835 ]
Sergey Chugunov commented on IGNITE-8131: ----------------------------------------- [~garus.d.g], I double checked your result and managed to reproduce the issue locally: I've run this single test with "Until failure" configuration and observed failure on 120th execution. I found another detail about failure: in all successful executions ZooKeeper client is closed because of session timeout reported by this line in logs: {noformat} [WARN ][zk-client-timer-internal.ZookeeperDiscoverySpiTest1][ZookeeperClient] Failed to establish ZooKeeper connection, close client [timeout=2000] {noformat} But in failed execution I don't see this line in the logs. It looks worth investigating what causes this behavior and its implications. > ZookeeperDiscoverySpiTest#testClientReconnectSessionExpire* tests fail on TC > ---------------------------------------------------------------------------- > > Key: IGNITE-8131 > URL: https://issues.apache.org/jira/browse/IGNITE-8131 > Project: Ignite > Issue Type: Bug > Components: zookeeper > Reporter: Sergey Chugunov > Assignee: Denis Garus > Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > Two tests always fail on TC with the assertion > {noformat} > junit.framework.AssertionFailedError: Failed to wait for disconnect/reconnect > event. > at > org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.waitReconnectEvent(ZookeeperDiscoverySpiTest.java:4221) > at > org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.reconnectClientNodes(ZookeeperDiscoverySpiTest.java:4183) > at > org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.clientReconnectSessionExpire(ZookeeperDiscoverySpiTest.java:2231) > at > org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testClientReconnectSessionExpire1_1(ZookeeperDiscoverySpiTest.java:2206) > {noformat} > from client disconnect/reconnect events check. Obviously client doesn't > generate these events as it supposed to do. > (TC runs can be found > [here|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgniteZooKeeperDiscovery&branch_IgniteTests24Java8=pull%2F3730%2Fhead&tab=buildTypeStatusDiv]). > It is possible to reproduce test failure locally as well, but with low > probability: one failure for 50 or even 300 successful executions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)