That is definitely on my list of concerns. However there are a couple of
issues to deal with. The actors are queried by front end users for
information and routing the traffic of every user to a single node would be
hazardous to stability. Furthermore, the actor could hold state that is
Hmm. In that case, that's not Cluster Sharding -- but it's also not
common, because it can be challenging to get right (without inconsistencies
between replicas) and I suspect *usually* will result in worse throughput.
(Since you're introducing a lot of PubSub traffic, and replicating the
They are updated from a DistributedPubSub topic. Each of them gets the
update messages and then recalculates the data they need to maintain
locally. So essentially they all function as independent actors, isolated
from each other, knowing nothing about each other. This object is one of
the
How are you coordinating state between logically-equal actors on different
physical nodes?
On Wednesday, June 1, 2016 at 3:24:57 PM UTC-6, kraythe wrote:
>
> So the reason I didn't think this was cluster sharding is that I actually
> want these supervisor actors (and their supervised children)
So the reason I didn't think this was cluster sharding is that I actually
want these supervisor actors (and their supervised children) to be
REPLICATED on every node (they handle user requests). Basically if there is
an actor with key 10, I want one actor with key 10 per node. I didn't want
Hmm, on one node? How Ok I will look at docs ... kind of thought I
might be reinventing the wheel? Can I send to one router and have the
message redirected to the actor with the right key ?
On Wednesday, June 1, 2016 at 3:42:16 PM UTC-5, Konrad Malawski wrote:
>
>
> I was working on a
I was working on a supervisor that lazy creates actors based on some key
and then will forward messages to that actor.
That's Cluster Sharding :-)
http://doc.akka.io/docs/akka/snapshot/scala/cluster-sharding.html
Technically you can use it on one node too, yeah.
Happy hAkking!
--
Konrad
I was working on a supervisor that lazy creates actors based on some key
and then will forward messages to that actor. However, it just seems like I
am doing something frightfully common. So I was wondering if anyone knows
something in Akka that already does this and I should use that. I have
