From 1bb8f1737f0983a7e20104ca13e133ebb41fc917 Mon Sep 17 00:00:00 2001 From: Patrik Nordwall Date: Tue, 8 Nov 2016 13:37:34 +0100 Subject: [PATCH] increase barrier-timeout in ClusterShardingSpec, #21718 * In the logs of the failing test we can see that the first node is removed as expected and then come back in the membership, which is possible in case of conflicting membership state merge. It is supposed to be removed again by the auto-down. That doesn't happen within the barrier-timeout. --- .../scala/akka/cluster/sharding/ClusterShardingSpec.scala | 1 + 1 file changed, 1 insertion(+) diff --git a/akka-cluster-sharding/src/multi-jvm/scala/akka/cluster/sharding/ClusterShardingSpec.scala b/akka-cluster-sharding/src/multi-jvm/scala/akka/cluster/sharding/ClusterShardingSpec.scala index 36a251628d..3e1c2bdba8 100644 --- a/akka-cluster-sharding/src/multi-jvm/scala/akka/cluster/sharding/ClusterShardingSpec.scala +++ b/akka-cluster-sharding/src/multi-jvm/scala/akka/cluster/sharding/ClusterShardingSpec.scala @@ -158,6 +158,7 @@ abstract class ClusterShardingSpecConfig( max-simultaneous-rebalance = 1 } } + akka.testconductor.barrier-timeout = 70s """)) nodeConfig(sixth) { ConfigFactory.parseString("""akka.cluster.roles = ["frontend"]""")