Static cluster nodes configuration - no discovery

Elastic Stack Elasticsearch
1

Hi there,

For our purpose we're looking for a static configuration of (seed) nodes.
As we always know where our nodes are, and we don't want to discover things
that are fixed.

What configuration parameter should I use?

Best regards,

Robin Verlangen
Software engineer
*
*
W http://www.robinverlangen.nl
E robin@us2.nl

http://goo.gl/Lt7BC

Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.

--

2

Hi,

I'm not an elasticsearch expert, just beginner :slight_smile:

Choose Unicast (
Elasticsearch Platform — Find real-time answers at scale | Elastic)

In your config file (elasticsearch.yml) you can

  • discovery.zen.ping.multicast.enabled: false
  • discovery.zen.ping.unicast.hosts: ["host1:portA", "host2:portB"] or
    simply [host1, host2] by example

Regards

Olivier

Le vendredi 25 janvier 2013 08:55:36 UTC+1, Robin Verlangen a écrit :

Hi there,

For our purpose we're looking for a static configuration of (seed) nodes.
As we always know where our nodes are, and we don't want to discover things
that are fixed.

What configuration parameter should I use?

Best regards,

Robin Verlangen
Software engineer
*
*
W http://www.robinverlangen.nl
E ro...@us2.nl <javascript:>

http://goo.gl/Lt7BC

Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.

--

3

That seems to be perfect. Thank you Olivier!

Best regards,

Robin Verlangen
Software engineer
*
*
W http://www.robinverlangen.nl
E robin@us2.nl

http://goo.gl/Lt7BC

Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.

On Fri, Jan 25, 2013 at 1:00 PM, Olivier L. olagache@gmail.com wrote:

Hi,

I'm not an elasticsearch expert, just beginner :slight_smile:

Choose Unicast (
Elasticsearch Platform — Find real-time answers at scale | Elastic)

In your config file (elasticsearch.yml) you can

  • discovery.zen.ping.multicast.enabled: false
  • discovery.zen.ping.unicast.hosts: ["host1:portA", "host2:portB"] or
    simply [host1, host2] by example

Regards

Olivier

Le vendredi 25 janvier 2013 08:55:36 UTC+1, Robin Verlangen a écrit :

Hi there,

For our purpose we're looking for a static configuration of (seed) nodes.
As we always know where our nodes are, and we don't want to discover things
that are fixed.

What configuration parameter should I use?

Best regards,

Robin Verlangen
Software engineer
*
*
W http://www.robinverlangen.nl
E ro...@us2.nl

http://goo.gl/Lt7BC

Disclaimer: The information contained in this message and attachments is
intended solely for the attention and use of the named addressee and may be
confidential. If you are not the intended recipient, you are reminded that
the information remains the property of the sender. You must not use,
disclose, distribute, copy, print or rely on this e-mail. If you have
received this message in error, please contact the sender immediately and
irrevocably delete this message and any copies.

--