If the current node count is always assumed as maximum count, the minimum_master_node condition N+1/2 would never be met :(
What you surely mean instead is that ES should remember cluster node count over time, and keeps the max value as the value for the formula. But that would mean you must not add nodes for spare which is also irritating, and the formula of N+1/2 must be the one and only true formula. But N+1/2 could be tightened to stronger split-brain risk mitigation - there is no reason why minimum_master_node should not be set to N so a cluster must always find all nodes before master election. Jörg -- 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGCJvs2-B%3Ddn3g52uM46Y7KvTAkS0dWS8%3DCDvYhBFyHXw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
