ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaliy Biryukov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-8182) ZookeeperDiscoverySpiTest#testRandomTopologyChanges_RestartZk fails on TC
Date Wed, 27 Jun 2018 10:36:00 GMT

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

Vitaliy Biryukov edited comment on IGNITE-8182 at 6/27/18 10:35 AM:
--------------------------------------------------------------------

Hi, [~sergey-chugunov]  please take a look.

This test falls for two reasons:
#  The bug in *curator-test*[1]. Scenario: in *TestingCluster* static block, some classes
are loaded and their bytecode rewrote. Further GC unload some classes and the next time the
classes will be loaded without bytecode rewriting. 
This scenario reproduces only in full test suite because some rewritten classes are used only
during star, stop or leader election.
This bug was fixed in latest versions of curator-test, but the new versions are not compatible
with ZooKeeper 3.4.x[2]. So I've added the workaround to *ZookeeperDiscoverySpiTestSuite1*.
#  Rarely ZK servers restarted too often and the connection does not have time to recover.

[IGNITE-8184|https://issues.apache.org/jira/browse/IGNITE-8184] can be closed as duplicate.

[1] https://github.com/Netflix/curator/issues/121
[2] https://curator.apache.org/zk-compatibility.html


was (Author: vitaliyb):
Hi, [~sergey-chugunov]  please take a look.

This test falls for two reasons:
#  The bug in curator-test[1]. Scenario: in TestingCluster static block, some classes are
loaded and their bytecode rewrote. Further GC unload some classes and the next time the classes
will be loaded without bytecode rewriting. 
This scenario reproduces only in full test suite because some rewritten classes are used only
during star, stop or leader election.
This bug was fixed in latest versions of curator-test, but the new versions are not compatible
with ZooKeeper 3.4.x[2]. So I've added the workaround to ZookeeperDiscoverySpiTestSuite1.
#  Rarely ZK servers restarted too often and the connection does not have time to recover.

[IGNITE-8184|https://issues.apache.org/jira/browse/IGNITE-8184] can be closed as duplicate.

[1] https://github.com/Netflix/curator/issues/121
[2] https://curator.apache.org/zk-compatibility.html

> ZookeeperDiscoverySpiTest#testRandomTopologyChanges_RestartZk fails on TC
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-8182
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8182
>             Project: Ignite
>          Issue Type: Bug
>          Components: zookeeper
>            Reporter: Sergey Chugunov
>            Assignee: Vitaliy Biryukov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>
> Test fails on TC with the following stack trace in logs:
> {noformat}
> org.apache.ignite.IgniteCheckedException: Failed to start manager: GridManagerAdapter
[enabled=true, name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
>     at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.randomTopologyChanges(ZookeeperDiscoverySpiTest.java:3791)
>     at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testRandomTopologyChanges_RestartZk(ZookeeperDiscoverySpiTest.java:2035)
> Caused by: org.apache.ignite.IgniteCheckedException: Failed to start SPI: ZookeeperDiscoverySpi
[zkRootPath=/apacheIgnite, zkConnectionString=127.0.0.1:45427,127.0.0.1:38620,127.0.0.1:45472,
joinTimeout=0, sesTimeout=30000, clientReconnectDisabled=false, internalLsnr=null]
>     at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.randomTopologyChanges(ZookeeperDiscoverySpiTest.java:3791)
>     at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testRandomTopologyChanges_RestartZk(ZookeeperDiscoverySpiTest.java:2035)
> Caused by: org.apache.ignite.spi.IgniteSpiException: Failed to initialize Zookeeper nodes
>     at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.randomTopologyChanges(ZookeeperDiscoverySpiTest.java:3791)
>     at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testRandomTopologyChanges_RestartZk(ZookeeperDiscoverySpiTest.java:2035)
> Caused by: org.apache.ignite.spi.discovery.zk.internal.ZookeeperClientFailedException:
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = ConnectionLoss
for /apacheIgnite
>     at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.randomTopologyChanges(ZookeeperDiscoverySpiTest.java:3791)
>     at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testRandomTopologyChanges_RestartZk(ZookeeperDiscoverySpiTest.java:2035)
> Caused by: org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
= ConnectionLoss for /apacheIgnite
>     at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.randomTopologyChanges(ZookeeperDiscoverySpiTest.java:3791)
>     at org.apache.ignite.spi.discovery.zk.internal.ZookeeperDiscoverySpiTest.testRandomTopologyChanges_RestartZk(ZookeeperDiscoverySpiTest.java:2035)
> {noformat}
> Reproducible on TC, investigation of failure conditions is needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message