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 new incoming request arrived in that actor will wait until the current process is done. On Monday, July 20, 2015 at 3:57:54 PM UTC-4, Jim Hazen wrote: > > 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 > track the logs and find out). And I don't mind not knowing. Akka does a > lot of work behind the scenes to rebalance as nodes add/drop from the > cluster. From a client perspective, things just work. > > Are you just curious about behavior, or have specific plans for this > information? > > On Mon, Jul 20, 2015 at 12:48 PM, Yifei <[email protected] <javascript:> > > wrote: > >> 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, Jim Hazen wrote: >>> >>> 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 actors. They'll be managed by 10 shards, across your ?? nodes. >>> >>> So seeing the creation of 100 actors and not 10, is expected. >>> >>> To get the number of actors managed by the shardRegion I assume you'd >>> need to discover the actors representing the shard regions and then size() >>> their children. I believe there is an internal messaging protocol for >>> doing this, but I don't have the docs in front of me. You probably also >>> find actors under the /user/sharding/ namespace using normal actor >>> selection. >>> >> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "Akka User List" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/akka-user/e0fqWMFzZuY/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
