How many nodes are you running, how many are master-eligible, and what's
your setting for discovery.zen.minimum_master_nodes?
Given a reasonable setting for minimum master nodes, any single node which
fails to join the rest of the cluster should refuse to form its own. From
there, health checks to the cluster root URL will return a 503 error,
causing HAProxy to take it out of the rotation.
On Thu, May 30, 2013 at 9:18 PM, Chad Kouse chad.kouse@gmail.com wrote:
We are trying to use HAProxy to ensure that if a node fails it is removed
from taking requests from our client. A problem we have run into with this
approach is in the case where a node has incorrectly detected a fault and
takes over as the master.
When this happens HAProxy thinks all nodes are up, but updates are
randomly going to one master or the other -- same with searches.
Is there an API we should use to detect when more than one node thinks
it's a master and try to determine what node should be removed from service?
Is there a better approach here than using HAProxy?
Thanks,
--chad
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Nick Zadrozny
http://websolr.com • http://bonsai.io
Hosted full-text search, with Solr and Elasticsearch.
Let's talk in real time: http://meetme.so/nz
--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.