New setup - 2nd node not connecting


(ElasticBeats) #1

Hi,

I have put together a small cluster for metricbeat. All is well so far but i cannot get the 2nd node to connect to the cluster, my config on the second node is:

======================== 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:

https://www.elastic.co/guide/en/elasticsearch/reference/index.html

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

Use a descriptive name for your cluster:

cluster.name: cluster1

Use a descriptive name for the node:

node.name: elastic2

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

Set the bind address to a specific IP (IPv4 or IPv6):

network.host: 192.168.51.71

Set a custom port for HTTP:

http.port: 9201

For more information, consult the network module documentation.

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

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

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

discovery.zen.ping.unicast.hosts: ["192.168.51.70:9201", "192.168.51.71:9201"]

Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):

#discovery.zen.minimum_master_nodes:

For more information, consult the zen discovery module documentation.

---------------------------------- Gateway -----------------------------------

Block initial recovery after a full cluster restart until N nodes are started:

#gateway.recover_after_nodes: 3

For more information, consult the gateway module documentation.

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

Require explicit names when deleting indices:

#action.destructive_requires_name: true
node.master: false
node.data: true

http.port: 9202

tcp.port: 9302

Cheers,


(Philani) #2

Hi there,

Please remove the ports from this field. Elasticsearch uses the 9300 ports for internal comms (including joining a cluster); 9201 would be for accepting traffic in your config, not for discovering cluster information. Leaving the hostnames/IP addresses in this field should be sufficient.

discovery.zen.ping.unicast.hosts: ["192.168.51.70", "192.168.51.71"]

/p


(ElasticBeats) #3

Eek! Amended configs, restarted, both online :slight_smile:

Thanks again!


(system) #4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.