address is now gated for [5000] ms

[Kostas kougios]

Hi, I am occasionally getting this when running tests. The test resumes, but I wait for 5 secs. Is there a config property to set it to 500ms?
(googling didn't reveal any relevant info)

Thanks

[Patrik Nordwall]

That is probably config property akka.remote.retry-gate-closed-for

/Patrik

--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

--

Patrik Nordwall
Typesafe -  Reactive apps on the JVM
Twitter: @patriknw

[Konstantinos Kougios]

Thanks Patrik, I tried it and it changes the gate wait, but has no effect in the overall wait :

2015-10-19 14:25:25,524 WARN  [akka.tcp://DataDistributionEndToEndTest@dist-index:2720/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FDataDistributionEndToEndTest%40dist-index%3A2721-0] a.r.ReliableDeliverySupervisor - REQ_ID: - Association with remote system [akka.tcp://DataDistributionEndToEndTest@dist-index:2721] has failed, address is now gated for [500] ms. Reason: [Association failed with [akka.tcp://DataDistributionEndToEndTest@dist-index:2721]] Caused by: [Connection refused: dist-index/192.168.0.11:2721]
waiting cluster
done waiting cluster, waited 10812 ms


The code that waits is for the code that awaits for the cluster actorsystems to be aware of each other:

val start=System.currentTimeMillis
awaitCond(
   cluster1.state.members.size == allClusters.size &&
      cluster2.state.members.size == allClusters.size &&
      cluster3.state.members.size == allClusters.size &&
      driverCluster.state.members.size == allClusters.size,
   60 seconds
)
val dt=System.currentTimeMillis - start
println(s"done waiting cluster, waited $dt ms")

Normally this takes 1-2 seconds. But when the gate issue occurs, it takes a lot more, i.e. 10 secs as per above.

Cheers

You received this message because you are subscribed to a topic in the Google Groups "Akka User List" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/akka-user/CTJyKGc_Qjo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to akka-user+...@googlegroups.com.

[Patrik Nordwall]

I'm afraid I don't know why you get the "association failure" in the first place or if it is related to the 10 sec delay.

/Patrik

[Konstantinos Kougios]

What I found out is that the issue was due to the way I was calling Cluster(system) for all the simulated servers.

Calling

val system1=....
val cluster1 = ....

val system2=....
val cluster2 = ....

...

creates the issue probably due to delays for system2 , 3 etc to open their ports. So a lot of clusters were "gating" each other addresses because the ports were not open. That caused sometimes delays to 10 secs even if gate wait was 500ms.

by doing

val system1=....
val system2=....
.....

val cluster1 = ....
val cluster2 = ....
...
and then clusterX.join(clusterY)

the issue doesn't occur anymore

Cheers

[Kostas kougios]

I am afraid I got that issue again. That's because actors internally need the cluster, so I can't enforce a sequence where all systems are created and then all clusters. Now I have to wait for 10 + secs for my tests to run despite my settings:

remote {
  retry-gate-closed-for = 500

akka {
  cluster.pub-sub.gossip-interval = 150ms