I am currently only running the actor that listens on a single node (local to the shard coordinator), but it would be easy to run it on multiple or all nodes. The allocation strategy had easy access to a list of all of the cluster nodes.
On Wed, Jul 1, 2015, 07:04 Brice Figureau <[email protected]> wrote: > Hi Brandon, > > On Tue, 2015-06-30 at 08:03 -0700, Brandon Arp wrote: > > Hi Brice, > > > > > > I had a similar need for operational visibility. The approach I took > > was to create a ShardAllocationStrategy and configure my cluster to > > use it. The strategy would save off the allocations so that they > > could inspected later. Specifically, the ShardAllocationStrategy took > > an ActorSelection and then sent a message with the state to the > > selection. The strategy has worked pretty well so far. > > This is a very smart trick! Thanks for sharing it. > > I started implementing this, but I was wondering where you were running > the ActorSelection in your cluster ? > Do you have this actor in only one place in your cluster, or one per > node ? > > Thanks! > > -- > Brice Figureau <[email protected]> > > -- >>>>>>>>>> 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.
