Log ------- I am seeing the defEventStoreSupervisorCoordinator and defEventStoreActorCoordinator but these are not storing into the cassandra db and when this microservice recevies the event it tries to register the coordinators dynamically.
------- ith configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.Worker Startup ########################### [INFO] [11/15/2015 14:24:12.704] [ClusterSystem-akka.actor.default-dispatcher-16] [akka.tcp://[email protected]:2552/system/sharding/defEventStoreSupervisorCoordinator] ClusterSingletonManager state change [Start -> Younger] [INFO] [11/15/2015 14:24:12.704] [ClusterSystem-akka.actor.default-dispatcher-18] [akka.tcp://[email protected]:2552/system/sharding/defEventStoreActorCoordinator] ClusterSingletonManager state change [Start -> Younger] ShardId --->36 [WARN] [11/15/2015 14:24:46.816] [ClusterSystem-akka.actor.default-dispatcher-25] [akka.tcp://[email protected]:2552/system/sharding/defEventStoreSupervisor] Trying to register to coordinator at [Some(ActorSelection[Anchor(akka.tcp://[email protected]:2550/), Path(/system/sharding/defEventStoreSupervisorCoordinator/singleton/coordinator)])], but no acknowledgement. Total [1] buffered m essages. [WARN] [11/15/2015 14:24:48.816] [ClusterSystem-akka.actor.default-dispatcher-18] [akka.tcp://[email protected]:2552/system/sharding/defEventStoreSupervisor] Trying to register to coordinator at [Some(ActorSelection[Anchor(akka.tcp://[email protected]:2550/), Path(/system/sharding/defEventStoreSupervisorCoordinator/singleton/coordinator)])], but no acknowledgement. Total [1] buffered m essages. On Sunday, November 15, 2015 at 2:08:54 PM UTC-5, sd d wrote: > > *Hello,* > > > *Source Code:* > > https://github.com/sdab75/spring-boot-akka-cluster-sharding > > > *Scenario:* > > > 1. Abc and Def are 2 micro services and they communicates with each > other through their respective Async Event Listeners ( these are 2 > services > are in the same cluster because they need to communicate with each other). > 2. Each microservice set up the following way. > - Akka-PubSub-Listener to consume event topic. > - And the Listener uses EventStoreSupervisor sharded region to hand > over the request to the respective EventStoreActor which stores the > validated event and further publish event for other microservice. > > *Issue:* > > > 1. Since these micro services (Abc and Def) does different things I > need to have to corresponding message extractors and sharded regions. But > when I start these micro services in the same cluster, only the first seed > node corresponding sharded region and coordinator gets created and started. > - Example: > - If Abc service is on 2550 and Def on 2551. I only see sharded > region and coordinator created for Abc microservice. > - If I put Def on 2550 then I can see Def corresponding > coordinator and region created. > > The only way to create different sharded regions and coordinators is to > put them on different clusters (i.e) each microservice will have its own > cluster setup. If I do this then microsevice’s can’t communicate with each > because they are not part of the same cluster. > > > How do I resolve this issue? I need persistence for my received events. > What is recommended paradigms in akka for this scenario. I am relatively > new to the akka world, please let me know if my understanding is incorrect > on akka cluster sharding. > > > Thanks, > > SD > > > -- >>>>>>>>>> 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.
