Transport vs Node client

Elastic Stack Elasticsearch
1

Hello,

I like the performance benefit that a Node client provides, in that it
avoids double-hops, but I like the quick startup of a Transport client
because it does not need to perform discovery. Will using
client.transport.sniff=true on a TransportClient give me the best of both
worlds?

Thanks,
Mark

2

No, sniff just means it will use the list of nodes you provide the transport client fetch all the other nodes and use as the nodes to round robin between (instead of only the list you provided). Note though, you need to create the NodeClient on application startup, and reuse it.

On Wednesday, March 7, 2012 at 7:41 AM, Mark Waddle wrote:

Hello,

I like the performance benefit that a Node client provides, in that it avoids double-hops, but I like the quick startup of a Transport client because it does not need to perform discovery. Will using client.transport.sniff=true on a TransportClient give me the best of both worlds?

Thanks,
Mark