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
On Thursday, 22 October 2015 23:33:46 UTC+1, Kostas kougios wrote:
>
> 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
>
>
>
--
>>>>>>>>>> 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.
