Master node not discovered yet

Elastic Search
1

I created a new node which i want to join an already existing single-node cluster. For the life of me i cannot make it work

The configuraiton file for the existing cluster is

cluster.name: syslog
node.name: syslog01
#path.data: /var/lib/elasticsearch
path.data: /data/elasticsearch
path.logs: /var/log/elasticsearch
path.repo: [ "/mnt/nas02" ]
#network.host: syslog.eksponent.com
network.host: _site_
http.port: 9200
#discovery.type: single-node
cluster.initial_master_nodes:
  - syslog01
  - syslog02  
xpack.security.enabled: true
xpack.security.http.ssl.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.http.ssl.key: certs/cert-key.pem
xpack.security.http.ssl.certificate: certs/cert.pem
#xpack.security.http.ssl.certificate_authorities: certs/intermediate.pem
xpack.security.transport.ssl.key: certs/cert-key.pem
xpack.security.transport.ssl.certificate: certs/cert.pem
#xpack.security.transport.ssl.certificate_authorities: certs/intermediate.pem
xpack.monitoring.collection.enabled: true
indices.breaker.request.limit: 41%
indices.breaker.total.use_real_memory: false

The conf file for the new node is:

cluster.name: syslog
node.name: syslog02
#path.data: /var/lib/elasticsearch
path.data: /data/elasticsearch
path.logs: /var/log/elasticsearch
#path.repo: [ "/mnt/nas02" ]
#network.host: syslog02.eksponent.com
network.host: _site_
http.port: 9200
discovery.seed_hosts:
  - 192.168.10.98:9200
  - syslog.eksponent.com
xpack.security.enabled: true
xpack.security.http.ssl.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.http.ssl.key: certs/cert-key.pem
xpack.security.http.ssl.certificate: certs/cert.pem
#xpack.security.http.ssl.certificate_authorities: certs/intermediate.pem
xpack.security.transport.ssl.key: certs/cert-key.pem
xpack.security.transport.ssl.certificate: certs/cert.pem
#xpack.security.transport.ssl.certificate_authorities: certs/intermediate.pem
xpack.security.transport.ssl.verification_mode: none # <-- Must be removed!!
xpack.monitoring.collection.enabled: true
indices.breaker.request.limit: 41%
indices.breaker.total.use_real_memory: false

The error is:

[2023-11-15T17:24:30,729][WARN ][o.e.d.PeerFinder ] [syslog02] address [192.168.10.98:9300], node [null], requesting [false] discovery result: [192.168.10.98:9300] connect_timeout[30s]
[2023-11-15T17:24:39,706][WARN ][o.e.c.c.ClusterFormationFailureHelper] [syslog02] master not discovered yet, this node has not previously joined a bootstrapped cluster, and [cluster.initial_master_nodes] is empty on this node: have discovered [{syslog02}{ZdLLyQijR2-f_IVQv77XFw}{YWcsVhinSQCWHqEty_DWJQ}{syslog02}{192.168.10.97}{192.168.10.97:9300}{cdfhilmrstw}{8.11.0}{7000099-8500003}]; discovery will continue using [192.168.10.98:9200, 192.168.10.98:9300] from hosts providers and [{syslog02}{ZdLLyQijR2-f_IVQv77XFw}{YWcsVhinSQCWHqEty_DWJQ}{syslog02}{192.168.10.97}{192.168.10.97:9300}{cdfhilmrstw}{8.11.0}{7000099-8500003}] from last-known cluster state; node term 0, last-accepted version 0 in term 0; for troubleshooting guidance, see Troubleshooting discovery | Elasticsearch Guide [8.11] | Elastic

2

You can't have a 2-node cluster. You have to go from 1 to 3. Otherwise, the two nodes cannot decide between themselves who the master will be.

3

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