Hello Endre, What about one actor from each node joining the DistributedPubSubMediator and this actor could register with a node local Akka eventbus? The sharded actors could register with the local Akka event bus for messages.
So a message published to a topic, on the DistributedPubSubMediator would be received by the local actor joined to DistributedPubSubMediator which would then publish the message to the local Akka eventbus. I think this would work. I'm assuming I'll have >10,000 actors per node, but don't know until the rest of the system is in place. Each actor will be storing GPS coordinates for a rectangular region and will be used as an index into Cassandra tables. On Monday, 5 May 2014 09:19:52 UTC+1, Akka Team wrote: > > Hi Jabbar, > > No, you are not missing anything, PubSub is designed for such cases. Just > be careful not to broadcast too much data since it does not scale linearily. > > -Endre > > > On Sat, May 3, 2014 at 1:06 AM, Jabbar Azam <[email protected]<javascript:> > > wrote: > >> I've just looked at the documentation. I can use the >> DistributedPubSubMediator and get all the sharded actors listening to a >> topic. So when I need the contents from a particular sharded actor I can >> send a message to a topic which will be received by all the sharded actors >> and the one containing the cache information will respond. >> >> Sounds too simple. I must be missing something... >> >> >> On Friday, 2 May 2014 21:25:17 UTC+1, Jabbar Azam wrote: >>> >>> Hello, >>> >>> I want to create a cluster of actors using the cluster sharding module. >>> I want to be able to send a message to all the actors in the cluster. I've >>> read the documentation and seen the typesafe Activator example which shows >>> messages being sent to individual actors. Does anybody know if it's >>> possible to broadcast a message to all the actors using cluster sharding? >>> >>> Basically I'm trying to implement a persistent distributed cache and I >>> want each cache element to respond to a broadcast message which where each >>> cache element(actor) has a resulting response. >>> >> -- >> >>>>>>>>>> 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] <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. >> > > > > -- > Akka Team > Typesafe - The software stack for applications that scale > Blog: letitcrash.com > Twitter: @akkateam > -- >>>>>>>>>> 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.
