Using ES' own load balancing functionality

Elastic Stack Elasticsearch
1

I'm a bit confused about one thing, reading the comments in
elasticsearch.yml:

3. You want this node to be neither master nor data node, but

to act as a "search load balancer" (fetching data from nodes,

aggregating results, etc.)

node.master: false

node.data: false

My questions are:

  1. So if I want to use this set up, should I just let my client know only
    this node?

  2. Then what happens when this node goes down?

Thanks.

--
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.

2

This is regarding 0.90.6 BTW.

On Wednesday, November 13, 2013 2:59:04 PM UTC-5, nfwlpw wrote:

I'm a bit confused about one thing, reading the comments in
elasticsearch.yml:

3. You want this node to be neither master nor data node, but

to act as a "search load balancer" (fetching data from nodes,

aggregating results, etc.)

node.master: false

node.data: false

My questions are:

  1. So if I want to use this set up, should I just let my client know only
    this node?

  2. Then what happens when this node goes down?

Thanks.

--
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.

3

I think your client would need to know about a set of such 'routing' nodes
and not just one node. This will ensure that if one or two nodes out of
that set go down, your application is still working fine. Choosing the set
size obviously is dependent on how much resiliency you want.

-Amit.

On Wed, Nov 13, 2013 at 11:59 AM, nfwlpw nfwlpw@gmail.com wrote:

This is regarding 0.90.6 BTW.

On Wednesday, November 13, 2013 2:59:04 PM UTC-5, nfwlpw wrote:

I'm a bit confused about one thing, reading the comments in
elasticsearch.yml:

3. You want this node to be neither master nor data node, but

to act as a "search load balancer" (fetching data from nodes,

aggregating results, etc.)

node.master: false

node.data: false

My questions are:

  1. So if I want to use this set up, should I just let my client know only
    this node?

  2. Then what happens when this node goes down?

Thanks.

--
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.

--
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.