Fixed cluster detection


(Robin Verlangen) #1

Hi there,

We're working on an application that embeds ES, however we want to have
full control over all aspects, we don't want to use something like
multicast for detection based on cluster name. We want to provide a
"manual" list of node IPs + ports to connect on.

Should we use discovery.zen.ping.unicast for this? How exactly will the
configuration look?

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.

--


(Martijn Van Groningen) #2

Hi Robin,

Unicast discovery is what you can use. You can disable multicast discovery
and add an initial node list in your elasticsearch.yml file or set these
options via your settings builder for the Java api:
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["host1", "host2:port",
"host3[portX-portY]"]

You need to configure this on each ES node. Each node initially needs to
know at least one other data node. Once the node is connected to the
cluster it automatically gets aware of the other nodes in the cluster. Also
make sure to use static ip addresses / hostnames in your configuration.

Martijn

On 25 September 2012 22:58, Robin Verlangen robin@us2.nl wrote:

Hi there,

We're working on an application that embeds ES, however we want to have
full control over all aspects, we don't want to use something like
multicast for detection based on cluster name. We want to provide a
"manual" list of node IPs + ports to connect on.

Should we use discovery.zen.ping.unicast for this? How exactly will the
configuration look?

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.

--

--
Met vriendelijke groet,

Martijn van Groningen

--


(Robin Verlangen) #3

Hi Marthijn,

Thank you for your response. That looks pretty good, we'll start working on
that.

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.

2012/9/26 Martijn v Groningen martijn.v.groningen@gmail.com

Hi Robin,

Unicast discovery is what you can use. You can disable multicast discovery
and add an initial node list in your elasticsearch.yml file or set these
options via your settings builder for the Java api:
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["host1", "host2:port",
"host3[portX-portY]"]

You need to configure this on each ES node. Each node initially needs to
know at least one other data node. Once the node is connected to the
cluster it automatically gets aware of the other nodes in the cluster. Also
make sure to use static ip addresses / hostnames in your configuration.

Martijn

On 25 September 2012 22:58, Robin Verlangen robin@us2.nl wrote:

Hi there,

We're working on an application that embeds ES, however we want to have
full control over all aspects, we don't want to use something like
multicast for detection based on cluster name. We want to provide a
"manual" list of node IPs + ports to connect on.

Should we use discovery.zen.ping.unicast for this? How exactly will
the configuration look?

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.

--

--
Met vriendelijke groet,

Martijn van Groningen

--

--


(system) #4