StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>No, by choice.</p> <p>Loadbalancing is based on many heuristics that differ per application. A lot of setups already have hardware/software loadbalancers in front of the elasticsearch cluster.</p> <p>On top of that elasticsearch already load balances so even if the client hits one node all the time, the cluster can let other nodes coordinate the search.</p> <p>Of course failover is something that needs to be handled in the application (if the hardware/loadbalancers don't already take care of this), I might release a simple implementation as a separate nuget package that can keep a pool of clients but for now my main focus is polishing NEST's API to be 1.0 stable/fully documented.</p> <p><strong>UPDATE 2014</strong></p> <p>Since NEST 1.0 cluster failover and connection pooling is built into the client:</p> <pre><code>var node = new Uri("http://mynode.example.com:8082/apiKey"); var connectionPool = new SniffingConnectionPool(new[] { node1, node2, node3 }); var config = new ConnectionConfiguration(connectionPool); var client = new ElasticsearchClient(config); </code></pre> <p><a href="http://nest.azurewebsites.net/elasticsearch-net/cluster-failover.html" rel="nofollow">http://nest.azurewebsites.net/elasticsearch-net/cluster-failover.html</a></p> <p><a href="http://nest.azurewebsites.net/elasticsearch-net/connecting.html" rel="nofollow">http://nest.azurewebsites.net/elasticsearch-net/connecting.html</a></p> <p><a href="http://nest.azurewebsites.net/nest/connecting.html" rel="nofollow">http://nest.azurewebsites.net/nest/connecting.html</a></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload