raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

increase barrier-timeout in ClusterShardingSpec, #21718

Browse source 
* 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.
This commit is contained in:
Patrik Nordwall 2016-11-08 13:37:34 +01:00
parent 72925ba392
commit 1bb8f1737f
1 changed files with 1 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
akka-cluster-sharding/src/multi-jvm/scala/akka/cluster/sharding/ClusterShardingSpec.scala
View file

@ -158,6 +158,7 @@ abstract class ClusterShardingSpecConfig(
max-simultaneous-rebalance = 1 max-simultaneous-rebalance = 1
} }
} }
akka.testconductor.barrier-timeout = 70s
""")) """))
nodeConfig(sixth) { nodeConfig(sixth) {
ConfigFactory.parseString("""akka.cluster.roles = ["frontend"]""") ConfigFactory.parseString("""akka.cluster.roles = ["frontend"]""")