3. All actions are routed automatically to the relevant shards only, no matter what client.
Just a comment about this. If you are using a TransportClient, the transport client won't try to reach directly the right shard. It will simply direct the request to a node which is one of the nodes it knows about (list of nodes you provided with addTransportAddress() method). The NodeClient will do that for sure. See http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/client.html#transport-client -- David Pilato | Technical Advocate | Elasticsearch.com @dadoonet | @elasticsearchfr Le 25 juillet 2014 à 09:59:38, [email protected] ([email protected]) a écrit: 1. No. ES is already managing connections, see TransportClient 2. REST API sits on top of native Java client. So, because of HTTP, you have overhead with REST. Async call API with HTTP is a mess. 3. All actions are routed automatically to the relevant shards only, no matter what client. 4. There are scala clients out there like elastic4s that wrap the native Java API, so I wonder why you do not use them? Jörg On Fri, Jul 25, 2014 at 8:25 AM, CB <[email protected]> wrote: hi all, i'm new to elastic search and would like to ask some basic questions. we are developing a system based on the play framework (non blocking io, event loop, scala) we are currently working with elastic search through the rest api which is working ok in dev. we are concerned about performance once we move to production environment. here are some questions: 1. can i point the rest api end point to a load balancer configured in front of the ES cluster? is that a common best practice? 2. is there any performance boost if we switch from rest api calls to native java client? if so - is it lagging behind with features? 3. java client - is this a smart client? meaning - can the client direct the queries to the relevant shard / shards for faster result retrieval? 4. any other advice / suggestion in regards to native client vs REST API for using ES? thanks! CB -- 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/3ca59232-8462-4e66-8400-8a5aca18fe0c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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/CAKdsXoHtVGgprA6gAGb81%2BdX7CLdWzq3ZgYYvT7c80nVnBro_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- 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/etPan.53d22551.520eedd1.13e40%40MacBook-Air-de-David.local. For more options, visit https://groups.google.com/d/optout.
