You could have only one routee per node that creates child actors and
delegates the actual work to them.
Another flexible and dynamic approach is to use Distributed Pub Sub as a
"router": http://doc.akka.io/docs/akka/2.4/scala/distributed-pub-sub.html
On Thu, Aug 25, 2016 at 11:20 PM, Cosmin
Thanks Patrik. I was hoping there would be a more flexible (and less hardcoded
way to do this)
> On 25 Aug 2016, at 18:41, Patrik Nordwall wrote:
>
> Start more worker actors on each node, each with a different name, let's say
> worker1, worker2, worker3. Then in
Start more worker actors on each node, each with a different name, let's
say worker1, worker2, worker3. Then in the config you define all 3 in the
paths
"paths": ["/user/worker1", "/user/worker2", "/user/worker3"]
/Patrik
On Thu, Aug 25, 2016 at 4:41 PM, Cosmin Marginean
Thanks, I will try to do further diagnosis, however this is a last resort.
I believe I would like to understand if this kind of use case is something
that Akka would natively be delivering in one form or another and / or if
I'm missing a trick in terms of correct router/etc that I'm using here.
Smells like the problem is somewhere in the router? I mean, if you're only
processing one message at a time, that suggests that you've only got one
instance of the worker Actor running, instead of the 100 that it's trying
to declare.
I don't use routers, so I can't speak to this config, but
Hi Muthu
I've explored these but they're not exactly what I'm after. The use case is
as follows: we have let's say 5 nodes, and 3 of them serve as "workers".
These 3 should be processing a series of events/messages in parallel.
We thus want some "load balancing" (consistent hashing is rigid
Hi Cosmin,
Are these what you are looking for
http://doc.akka.io/docs/akka/snapshot/scala/routing.html#ConsistentHashingPool_and_ConsistentHashingGroup
OR
http://doc.akka.io/docs/akka/snapshot/scala/routing.html#BroadcastPool_and_BroadcastGroup
Regards
Muthu
On Thursday, 25 August 2016