When I see this message, does it mean the leader node is not doing its job?
I see that there is a similar jira filed here:
https://github.com/akka/akka/issues/18368
We are using Akka 2.5.9.
Could you advise if this is a known issue and if there is any workaround?
Thanks,
on? What's the advantage of having a node join the weakly up state as part
of the cluster versus to just wait in the joining state until it is moved
into the Up state?
Thanks,
Grace
--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>
seconds.
If we go with router inside each client, do you have a suggestion which routing
machanism we use for fairer distribution? We are using pool instead of group
and we are currently using round-robin-pool. Haven't tested under heavy load
yet. Would round robin be a good choice?
Thanks,
such?
Or is this below design already sufficient for proper balanced routing?
Thanks,
Grace
package com.packt.akka.loadBalancing
import com.packt.akka.commons.Add
object LoadBalancingApp extends App {
//initiate three nodes from backend
Backend.initiate(2551)
Backend.initiate