Hello Jeroen, Indeed the options that you have listed are the other available, thus recommended, options. Truth be told, keeping a large cluster running does require some more tooling, ops skills or people to take care of it. In practice you could hook into monitoring services like Nagios or Zabbix to get more information about your cluster and react to it, by for example downing a certain set of nodes because of some SLA rule etc... It's hard to give a completely generic advice here; And in some apps, where you value consistency over everything else, manual downing may well be a feasible option. It all depends on your apps and use cases.
I'd highly recommend reading the thread "quorum based split brain resolution" on akka-user<https://groups.google.com/forum/#!searchin/akka-user/split$20brain/akka-user/UBSF3QQnGaM/JzFOzQc8NigJ> where Roland goes over the options that you have available. It's worth keeping in mind that *"everything is a trade-off"™. *You will be basically trading off either *availability* or *consistency* in one way or another. -- Cheers, Konrad 'ktoso' Malawski hAkker - Typesafe, Inc <http://scaladays.org> -- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
