I deployed to Prod but I realized about this situation and wonder if I am safe. It is a cluster deployed on AWS with persistent actors. I am using ClusterSharding for remoting which creates a ShardCoordinator. I also have implemented a Keep Majority Split Brain. The question is this: when there is a network issue and node B kills himself and the cluster marks it as down, later Message1 is sent to node A and the Coordinator of node A detects Message1 should be sent to existing entity in node B (that was downed), it blows up! Should I do something at all??? Or when node B is down, then the Coordinator somehow cleared all state regarding node B and keeps working? Is there only 1 instance of a ShardCoordinator in the entire cluster? What if is was in B (the node downed)?
Thanks, Sebastian. -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
