Elasticsearch cluster new Node addition error

[saxena_shk7 (Shikhar)]

I am trying to add third node in my elasticsearch existing cluster, but is unable to do so. I have tried everything from uncommenting transport.host option and setting it to 0.0.0.0 also setting discovery.seed_host to master-node IP but still its giving this error

[Tortoise]

Could you please share the uncommented entries from elasticsearch.yml in order to review further. Also on the 3 node which you want to add it should be using reconfigure command.

/usr/share/elasticsearch/bin/elasticsearch-reconfigure-node --enrollment-token

[saxena_shk7 (Shikhar)]

======================== Elasticsearch Configuration =========================

NOTE: Elasticsearch comes with reasonable defaults for most settings.

Before you set out to tweak and tune the configuration, make sure you

understand what are you trying to accomplish and the consequences.

The primary way of configuring a node is via this file. This template lists

the most important settings you may want to configure for a production cluster.

Please consult the documentation for further information on configuration options:

Elasticsearch Guide | Elastic

---------------------------------- Cluster -----------------------------------

Use a descriptive name for your cluster:

#cluster.name: my-application

------------------------------------ Node ------------------------------------

Use a descriptive name for the node:

#node.name: node-1

Add custom attributes to the node:

#node.attr.rack: r1

----------------------------------- Paths ------------------------------------

Path to directory where to store the data (separate multiple locations by comma):

path.data: /var/lib/elasticsearch

Path to log files:

path.logs: /var/log/elasticsearch

----------------------------------- Memory -----------------------------------

Lock the memory on startup:

#bootstrap.memory_lock: true

Make sure that the heap size is set to about half the memory available

on the system and that the owner of the process is allowed to use this

limit.

Elasticsearch performs poorly when the system is swapping the memory.

---------------------------------- Network -----------------------------------

By default Elasticsearch is only accessible on localhost. Set a different

address here to expose this node on the network:

#network.host: 192.168.0.1

By default Elasticsearch listens for HTTP traffic on the first free port it

finds starting at 9200. Set a specific HTTP port here:

#http.port: 9200

For more information, consult the network module documentation.

--------------------------------- Discovery ----------------------------------

Pass an initial list of hosts to perform discovery when this node is started:

The default list of hosts is ["127.0.0.1", "[::1]"]

discovery.seed_hosts: ["196.1.111.61:9300"]

Bootstrap the cluster using an initial set of master-eligible nodes:

#cluster.initial_master_nodes: ["node-1", "node-2"]

For more information, consult the discovery and cluster formation module documentation.

---------------------------------- Various -----------------------------------

Allow wildcard deletion of indices:

#action.destructive_requires_name: false

this is my config file for Node-3 and i already ran this command of elasticsearch-reconfigure-node --enrollment token

[Tortoise]

Hello,

Thank you for the details. Below are the parameters should be uncommented :

cluster.name: ***** (from my master or original running node)
node.name: node3
network.host: IP address of this host
http.port: 9200
transport.host: 0.0.0.0
discovery.seed_hosts:

• 1.1.1.1

Thanks,

[saxena_shk7 (Shikhar)]

Thanks for your reply, but still after changing the above parameters its giving this error.

======================== Elasticsearch Configuration =========================

NOTE: Elasticsearch comes with reasonable defaults for most settings.

Before you set out to tweak and tune the configuration, make sure you

understand what are you trying to accomplish and the consequences.

The primary way of configuring a node is via this file. This template lists

the most important settings you may want to configure for a production cluster.

Please consult the documentation for further information on configuration options:

Elasticsearch Guide | Elastic

---------------------------------- Cluster -----------------------------------

Use a descriptive name for your cluster:

cluster.name: ims-cluster

------------------------------------ Node ------------------------------------

Use a descriptive name for the node:

node.name: node-3

Add custom attributes to the node:

#node.attr.rack: r1

----------------------------------- Paths ------------------------------------

Path to directory where to store the data (separate multiple locations by comma):

path.data: /var/lib/elasticsearch

Path to log files:

path.logs: /var/log/elasticsearch

----------------------------------- Memory -----------------------------------

Lock the memory on startup:

#bootstrap.memory_lock: true

Make sure that the heap size is set to about half the memory available

on the system and that the owner of the process is allowed to use this

limit.

Elasticsearch performs poorly when the system is swapping the memory.

---------------------------------- Network -----------------------------------

By default Elasticsearch is only accessible on localhost. Set a different

address here to expose this node on the network:

network.host: 196.1.111.65

By default Elasticsearch listens for HTTP traffic on the first free port it

finds starting at 9200. Set a specific HTTP port here:

http.port: 9200
transport.host: 0.0.0.0

For more information, consult the network module documentation.

--------------------------------- Discovery ----------------------------------

Pass an initial list of hosts to perform discovery when this node is started:

The default list of hosts is ["127.0.0.1", "[::1]"]

discovery.seed_hosts:

• 196.1.111.61

Bootstrap the cluster using an initial set of master-eligible nodes:

#cluster.initial_master_nodes: ["node-1", "node-2"]

For more information, consult the discovery and cluster formation module documentation.

---------------------------------- Various -----------------------------------

Allow wildcard deletion of indices:

#action.destructive_requires_name: false

[Tortoise]

Hello,

Please check below documents

This node doesn't appear to be auto-configured for security. Expected configuration is missing from elasticsearch.yml

Kindly Help, While the Elasticsearch is with the default elasticsearch.yml it is giving such error /usr/share/elasticsearch/bin/elasticsearch-reconfigure-node --enrollment-token Generates all the necessary security configuration for a node in a secured cluster Option Description -E Configure a setting --enrollment-token The enrollment token to use -h, --help Show help -s, --silent Show minimal output -v, --verbose Show verbose output ERROR: Abor…

https://discuss.elastic.co/t/not-able-to-add-node-to-existing-cluster/348068/9

Add and remove nodes in your cluster | Elasticsearch Guide [8.15] | Elastic

Thanks

[saxena_shk7 (Shikhar)]

Thanks for the above reply!!! even after trying the above methods it is showing error that the master node is not reachable , i dont know if this is a bug or what because both the nodes are in the same subnet and even ports are opened and there is no firewall configuration applied.

[Tortoise]

Hello,

Seems some issue related as raised below :

Unable to generate a enrollement token with scope level to node ERROR: Failed to determine the health of the cluster. , with exit code 69

This and this don't match up. You shouldn't be able to access your cluster via http (non-SSL) if your node has SSL enabled.

Thanks

[saxena_shk7 (Shikhar)]

Finally problem solved. I have reinstalled the elasticsearch by downloadinging its zip package, I think its a bug. Anyways thanks @Tortoise.