ServerFailureRetrySingleOwnerTest can have issues creating cache managers ------------------------------------------------------------------------- Key: ISPN-4478 URL: https://issues.jboss.org/browse/ISPN-4478 Project: Infinispan Issue Type: Bug Security Level: Public(Everyone can see) Components: Remote Protocols Reporter: Galder Zamarreño Assignee: Galder Zamarreño Labels: testsuite_stability Fix For: 7.0.0.Alpha5 {code} java.lang.RuntimeException: Timed out before caches had complete views. Expected 3 members in each view. Views are as follows: [[ServerFailureRetrySingleOwnerTest-NodeD-62958, ServerFailureRetrySingleOwnerTest-NodeE-52896], [ServerFailureRetrySingleOwnerTest-NodeE-52896, ServerFailureRetrySingleOwnerTest-NodeF-14197], [ServerFailureRetrySingleOwnerTest-NodeE-52896, ServerFailureRetrySingleOwnerTest-NodeF-14197]] at org.infinispan.test.TestingUtil.viewsTimedOut(TestingUtil.java:268) at org.infinispan.test.TestingUtil.viewsTimedOut(TestingUtil.java:258) at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:250) at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:291) at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:922) at org.infinispan.test.MultipleCacheManagersTest.waitForClusterToForm(MultipleCacheManagersTest.java:226) at org.infinispan.test.MultipleCacheManagersTest.waitForClusterToForm(MultipleCacheManagersTest.java:233) at org.infinispan.client.hotrod.retry.AbstractRetryTest.createCacheManagers(AbstractRetryTest.java:63) at org.infinispan.test.MultipleCacheManagersTest.callCreateCacheManagers(MultipleCacheManagersTest.java:70) at org.infinispan.test.MultipleCacheManagersTest.createBeforeMethod(MultipleCacheManagersTest.java:80) at org.infinispan.client.hotrod.HitsAwareCacheManagersTest.createBeforeMethod(HitsAwareCacheManagersTest.java:35) {code} In the logs, you see messages like this: {code} [22:43:33] : [org.infinispan:infinispan-client-hotrod] 22:43:33,977 ERROR [StateConsumerImpl] (transport-thread-ServerFailureRetrySingleOwnerTest-NodeE-p848-t1:) ISPN000208: No live owners found for segment 0 of cache __cluster_registry_cache__. Current owners are: [ServerFailureRetrySingleOwnerTest-NodeD-62958]. Faulty owners: [ServerFailureRetrySingleOwnerTest-NodeD-62958] [22:43:33] : [org.infinispan:infinispan-client-hotrod] 22:43:33,977 ERROR [StateConsumerImpl] (transport-thread-ServerFailureRetrySingleOwnerTest-NodeE-p848-t1:) ISPN000208: No live owners found for segment 1 of cache __cluster_registry_cache__. Current owners are: [ServerFailureRetrySingleOwnerTest-NodeD-62958]. Faulty owners: [ServerFailureRetrySingleOwnerTest-NodeD-62958] [22:43:33] : [org.infinispan:infinispan-client-hotrod] 22:43:33,977 ERROR [StateConsumerImpl] (transport-thread-ServerFailureRetrySingleOwnerTest-NodeE-p848-t1:) ISPN000208: No live owners found for segment 2 of cache __cluster_registry_cache__. Current owners are: [ServerFailureRetrySingleOwnerTest-NodeD-62958]. Faulty owners: [ServerFailureRetrySingleOwnerTest-NodeD-62958] [22:43:33] : [org.infinispan:infinispan-client-hotrod] 22:43:33,977 ERROR [StateConsumerImpl] (transport-thread-ServerFailureRetrySingleOwnerTest-NodeE-p848-t1:) ISPN000208: No live owners found for segment 3 of cache __cluster_registry_cache__. Current owners are: [ServerFailureRetrySingleOwnerTest-NodeD-62958]. Faulty owners: [ServerFailureRetrySingleOwnerTest-NodeD-62958] [22:43:33] : [org.infinispan:infinispan-client-hotrod] 22:43:33,977 ERROR [StateConsumerImpl] (transport-thread-ServerFailureRetrySingleOwnerTest-NodeE-p848-t1:) ISPN000208: No live owners found for segment 4 of cache __cluster_registry_cache__. Current owners are: [ServerFailureRetrySingleOwnerTest-NodeD-62958]. Faulty owners: [ServerFailureRetrySingleOwnerTest-NodeD-62958] {code} The fact that after each method a cache manager is created might be causing issues here. According to test ServerFailureRetrySingleOwnerTest.testRetryPutIfAbsent runs fine and the next time createBeforeMethod is called, the issue appears. By doing creating the cache managers a single time, on test class startup, we should be able to speed up execution too.