Client question


(Mohit Anchlia) #1

Which is better for performance embedded client or transport client? How
should one decide which one to use?

And, how does embedded client join the cluster?


(Shay Banon) #2

What are you missing in the explanation here:
http://www.elasticsearch.org/guide/reference/java-api/client.html.

On Wed, May 16, 2012 at 9:21 PM, Mohit Anchlia mohitanchlia@gmail.comwrote:

Which is better for performance embedded client or transport client? How
should one decide which one to use?

And, how does embedded client join the cluster?


(Mohit Anchlia) #3

Looks like embedded client is preferred, but I don't understand how
Transport client causes 2 hops but embedded client doesn't? Data still need
to be streamed correct?

On Thu, May 17, 2012 at 3:15 PM, Shay Banon kimchy@gmail.com wrote:

What are you missing in the explanation here:
http://www.elasticsearch.org/guide/reference/java-api/client.html.

On Wed, May 16, 2012 at 9:21 PM, Mohit Anchlia mohitanchlia@gmail.comwrote:

Which is better for performance embedded client or transport client? How
should one decide which one to use?

And, how does embedded client join the cluster?


(Shay Banon) #4

Data is sent in any case yes. Lets take indexing for example, the node
client will know exactly which shard to index into, and will send the
indexing request directly to it. The transport client will simply pick one
of the nodes, and send the request to it, if that node holds the relevant
shard, thats great, if not, the node will redirect the request to the
relevant node where the shard exists.

On Fri, May 18, 2012 at 1:29 AM, Mohit Anchlia mohitanchlia@gmail.comwrote:

Looks like embedded client is preferred, but I don't understand how
Transport client causes 2 hops but embedded client doesn't? Data still need
to be streamed correct?

On Thu, May 17, 2012 at 3:15 PM, Shay Banon kimchy@gmail.com wrote:

What are you missing in the explanation here:
http://www.elasticsearch.org/guide/reference/java-api/client.html.

On Wed, May 16, 2012 at 9:21 PM, Mohit Anchlia mohitanchlia@gmail.comwrote:

Which is better for performance embedded client or transport client? How
should one decide which one to use?

And, how does embedded client join the cluster?


(Mohit Anchlia) #5

got it. Thanks!

On Sun, May 20, 2012 at 1:11 PM, Shay Banon kimchy@gmail.com wrote:

Data is sent in any case yes. Lets take indexing for example, the node
client will know exactly which shard to index into, and will send the
indexing request directly to it. The transport client will simply pick one
of the nodes, and send the request to it, if that node holds the relevant
shard, thats great, if not, the node will redirect the request to the
relevant node where the shard exists.

On Fri, May 18, 2012 at 1:29 AM, Mohit Anchlia mohitanchlia@gmail.comwrote:

Looks like embedded client is preferred, but I don't understand how
Transport client causes 2 hops but embedded client doesn't? Data still need
to be streamed correct?

On Thu, May 17, 2012 at 3:15 PM, Shay Banon kimchy@gmail.com wrote:

What are you missing in the explanation here:
http://www.elasticsearch.org/guide/reference/java-api/client.html.

On Wed, May 16, 2012 at 9:21 PM, Mohit Anchlia mohitanchlia@gmail.comwrote:

Which is better for performance embedded client or transport client?
How should one decide which one to use?

And, how does embedded client join the cluster?


(system) #6