Node id/name

Elastic Stack Elasticsearch
1

Hi,
Currently node id and name change at each restart. Is it possible to store
them (at least id) and reuse that node id? We are planning to monitor ES
cluster, nodes, indices and etc. However, since node id change every time it
is restarted, it is not possible to track a node.

--
Mustafa Sener
www.ifountain.com

1 Like
2

Node name can be set by setting name setting, id is always auto generated (its highly important to make sure its unique). It can be allowed to be set, but I wonder if a different way to try and attack this is not better, for example, I have been thinking that node level APIs should allow to specify the name (or even IP address) for example.

On Friday, June 10, 2011 at 3:20 PM, Mustafa Sener wrote:

Hi,
Currently node id and name change at each restart. Is it possible to store them (at least id) and reuse that node id? We are planning to monitor ES cluster, nodes, indices and etc. However, since node id change every time it is restarted, it is not possible to track a node.

--
Mustafa Sener
www.ifountain.com (http://www.ifountain.com)

3

Hi,
I understand your concerns about auto generated id. However, once it is auto
generated why we don't save it to meta data and reuse that auto generated id
instead of generating new one. In this way we can be sure that it is unique
since it is generated randomly once and we can refer to that node with that
id for subsequent restarts.

On Fri, Jun 10, 2011 at 5:54 PM, Shay Banon shay.banon@elasticsearch.comwrote:

Node name can be set by setting name setting, id is always auto
generated (its highly important to make sure its unique). It can be allowed
to be set, but I wonder if a different way to try and attack this is not
better, for example, I have been thinking that node level APIs should allow
to specify the name (or even IP address) for example.

On Friday, June 10, 2011 at 3:20 PM, Mustafa Sener wrote:

Hi,
Currently node id and name change at each restart. Is it possible to store
them (at least id) and reuse that node id? We are planning to monitor ES
cluster, nodes, indices and etc. However, since node id change every time it
is restarted, it is not possible to track a node.

--
Mustafa Sener
www.ifountain.com

--
Mustafa Sener
www.ifountain.com
WebRep
Overall rating

4

Since then we need to somehow identify a "machine" or an instance (basically a JVM) and then it becomes much more complex. I was thinking about stats reports, you can use things like IP, or hostname, to report it, or, node name if needed, which you can set.

On Monday, June 13, 2011 at 9:07 AM, Mustafa Sener wrote:

Hi,
I understand your concerns about auto generated id. However, once it is auto generated why we don't save it to meta data and reuse that auto generated id instead of generating new one. In this way we can be sure that it is unique since it is generated randomly once and we can refer to that node with that id for subsequent restarts.

On Fri, Jun 10, 2011 at 5:54 PM, Shay Banon <shay.banon@elasticsearch.com (mailto:shay.banon@elasticsearch.com)> wrote:

Node name can be set by setting name setting, id is always auto generated (its highly important to make sure its unique). It can be allowed to be set, but I wonder if a different way to try and attack this is not better, for example, I have been thinking that node level APIs should allow to specify the name (or even IP address) for example.

On Friday, June 10, 2011 at 3:20 PM, Mustafa Sener wrote:

Hi,
Currently node id and name change at each restart. Is it possible to store them (at least id) and reuse that node id? We are planning to monitor ES cluster, nodes, indices and etc. However, since node id change every time it is restarted, it is not possible to track a node.

--
Mustafa Sener
www.ifountain.com (http://www.ifountain.com)

--
Mustafa Sener
www.ifountain.com (http://www.ifountain.com)
WebRep

Overall rating

5

On Jun 10, 4:54 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Node name can be set by setting name setting, id is always auto generated (its highly important to make sure its unique). It can be allowed to be set, but I wonder if a different way to try and attack this is not better, for example, I have been thinking that node level APIs should allow to specify the name (or even IP address) for example.

And how exactly can I set it? I tried

node:
name: test

but it didn't work ...

6

Just using name, no node prefix.

On Wednesday, June 22, 2011 at 6:05 PM, Thomas Witt wrote:

On Jun 10, 4:54 pm, Shay Banon <shay.ba...@elasticsearch.com (http://elasticsearch.com)> wrote:

Node name can be set by setting name setting, id is always auto generated (its highly important to make sure its unique). It can be allowed to be set, but I wonder if a different way to try and attack this is not better, for example, I have been thinking that node level APIs should allow to specify the name (or even IP address) for example.

And how exactly can I set it? I tried

node:
name: test

but it didn't work ...

7

On Jun 22, 6:59 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Just using name, no node prefix.

Great, that worked. Thanks a lot for the help. AFAIK this is not
documented anyway, just FYI.