The idea to have three "node groups" (each with one master + N data nodes) sounds good. In this situation quorum will work fine. Combinded with a "read-only" instead of "inoperable" behaviour it would be great.
It is not ideal but I think I can convince the ops team to add a third group to the cluster. The other solution would be to blow up ES with functionality that Cassandra has (DC replication etc)... I think, that's off topic. ;) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d8d6b8c9-5776-46d8-b712-61f172dedc0b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
