[akka-user][deprecated] Error message: New incarnation of existing member is trying to join. Existing will be removed from the cluster and then new member will be allowed to join.

2018-04-01 Thread Grace
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,

[akka-user] Question on the WeaklyUp state

2018-03-07 Thread Grace
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/ >>>

Re: [akka-user] Question on Akka router

2018-02-22 Thread Grace
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,

[akka-user] Question on Akka router

2018-02-16 Thread Grace
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