To increase capacity you'll be scaling out nodes, not shard regions.
Shards are logical managers/buckets, they help organize and support the
actual processing actors, but it's those actors that are distributed.
You'll have one for each unique message destination, regardless of your
number of
Thanks Jim,
I planned to use the information to monitor the load of the actors and
shards. For example, to check if the actors are eating all the resources on
this host, if I should scale up the shardregion
Also, do you know if I can make the actor run in single-thread mode? As a
result, the n
It might be possible to find out, however why is this important to you?
The point of Akka cluster sharding is that shard management, handler actor
management and message routing, is all transparent. I use this facility in
my work and I don't know what nodes are handling what requests (sure I can
t
Thanks Jim,
It helps a lot.
Assuming I have 3 shardRegions running on 3 nodes with the same shard name.
Can I know the relationship between a shard and a shardRegion? For example,
can I know if shard#3 is under shardRegion@host2?
Thanks,
Yifei
On Monday, July 20, 2015 at 3:16:24 PM UTC-4,
There will be a new actor activated for each unique messageId destination.
Messages will arrive at that actor for processing. Actors are grouped
into shards, which help manage those actors. If you send 100 messages to
unique destinations across your cluster, they'll be handled by 100 unique
