On Monday, February 27, 2017 at 10:11:59 AM UTC-8, Justin du coeur wrote: > > There's no silver-bullet option for "fault tolerance" in situations like > this. You absolutely do *not* want to start up alternate versions of the > sharded entities in this situation -- that's classic split-brain, and is > the surest route to data corruption. > yes, this is a dangerous route. But what is the a way to manage cluster? I mean roll out of a new version or scaling down. In such situations one has to stop akka (or whole node).
-- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
