[WARN ][o.e.c.c.ClusterFormationFailureHelper] [node1] master not discovered yet, this node has not previously joined a bootstrapped cluster

Elastic Stack Elasticsearch
1

Hi Team,
I am using ES 8.6 version and configured 3 nodes,while starting the node i'am getting master not discovered yet exception.
This is my elastic .yml given below.

cluster.name: es-8_6
node.name: node1
path.data: /home/raghul/8.6/w1/data
path.logs: /home/raghul/8.6/w1/logs
network.host: 
cluster.initial_master_nodes: [ "node1", "node2", "node3" ]
discovery.seed_hosts: [ "","" ]
node.roles: [ data, master ]
http.port: 
readiness.port: 
xpack.security.enabled: false
xpack.security.transport.ssl.enabled: false
2

can you give a solution for this exception.

3

What do your logs show?

Also please format your code/logs/config using the </> button, or markdown style back ticks. It helps to make things easy to read which helps us help you :slight_smile:

4 
[2023-04-04T08:58:52,078][INFO ][o.e.t.n.NettyAllocator   ] [node1] creating NettyAllocator with the following configs: [name=unpooled, suggested_max_allocation_size=1mb, factors={es.unsafe.use_unpooled_allocator=null, g1gc_enabled=true, g1gc_region_size=4mb, heap_size=512mb}]
[2023-04-04T08:58:52,097][INFO ][o.e.i.r.RecoverySettings ] [node1] using rate limit [40mb] with [default=40mb, read=0b, write=0b, max=0b]
[2023-04-04T08:58:52,132][INFO ][o.e.d.DiscoveryModule    ] [node1] using discovery type [multi-node] and seed hosts providers [settings]
[2023-04-04T08:58:53,129][INFO ][o.e.n.Node               ] [node1] initialized
[2023-04-04T08:58:53,130][INFO ][o.e.n.Node               ] [node1] starting ...
[2023-04-04T08:58:53,154][INFO ][o.e.x.s.c.f.PersistentCache] [node1] persistent cache index loaded
[2023-04-04T08:58:53,156][INFO ][o.e.x.d.l.DeprecationIndexingComponent] [node1] deprecation component started
[2023-04-04T08:58:53,251][INFO ][o.e.t.TransportService   ] [node1] publish_address {<ip>:9300}, bound_addresses {<ip>:9300}
[2023-04-04T08:58:53,405][INFO ][o.e.b.BootstrapChecks    ] [node1] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2023-04-04T08:58:53,408][INFO ][o.e.c.c.ClusterBootstrapService] [node1] this node has not joined a bootstrapped cluster yet; [cluster.initial_master_nodes] is set to [node1, node2, node3]
[2023-04-04T08:59:03,419][WARN ][o.e.c.c.ClusterFormationFailureHelper] [node1] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [node1, node2, node3] to bootstrap a cluster: have discovered [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}]; discovery will continue using [<ip>:9271, <ip>:9272] from hosts providers and [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
[2023-04-04T08:59:13,423][WARN ][o.e.c.c.ClusterFormationFailureHelper] [node1] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [node1, node2, node3] to bootstrap a cluster: have discovered [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}]; discovery will continue using [<ip>:9271, <ip>:9272] from hosts providers and [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
[2023-04-04T08:59:23,420][WARN ][o.e.n.Node               ] [node1] timed out while waiting for initial discovery state - timeout: 30s
[2023-04-04T08:59:23,424][WARN ][o.e.c.c.ClusterFormationFailureHelper] [node1] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [node1, node2, node3] to bootstrap a cluster: have discovered [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}]; discovery will continue using [<ip>:9271, <ip>:9272] from hosts providers and [{node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
[2023-04-04T08:59:23,425][INFO ][o.e.h.AbstractHttpServerTransport] [node1] publish_address {<ip>:9230}, bound_addresses {<ip>:9230}
[2023-04-04T08:59:23,426][INFO ][o.e.n.Node               ] [node1] started {node1}{8de84vy4Sga7GSIv4Ucn7A}{105wmLVdTa2GzcTXIjsFzA}{node1}{<ip>}{<ip>:9300}{dm}{xpack.installed=true}
[2023-04-04T08:59:28,878][INFO ][o.e.x.m.p.NativeController] [node1] Native controller process has stopped - no new native processes can be started
[2023-04-04T08:59:28,879][INFO ][o.e.n.Node               ] [node1] stopping ...
[2023-04-04T08:59:28,883][INFO ][o.e.r.ReadinessService   ] [node1] stopping readiness service on channel None
[2023-04-04T08:59:28,884][INFO ][o.e.r.ReadinessService   ] [node1] readiness service stopped
[2023-04-04T08:59:28,886][INFO ][o.e.x.w.WatcherService   ] [node1] stopping watch service, reason [shutdown initiated]
[2023-04-04T08:59:28,887][INFO ][o.e.x.w.WatcherLifeCycleService] [node1] watcher has stopped and shutdown
[2023-04-04T08:59:29,391][INFO ][o.e.n.Node               ] [node1] stopped
[2023-04-04T08:59:29,392][INFO ][o.e.n.Node               ] [node1] closing ...
[2023-04-04T08:59:29,403][INFO ][o.e.n.Node               ] [node1] closed
5

Can you curl the master node from that one to check connectivity?

6

These port numbers look strange. How have you configured discovery.seed_hosts?

Are there any settings you have left out from what you posted earlier?

1 Like
7

but,I have same yml configuration in 7.17, it's working.

8

Elasticsearch communicates internally over port 9300, not 9200. It looks like you may be using custom HTTP port numbers and I am wondering if you may have incorrectly configured these in discovery.seed_hosts as ports in the 9200-9299 range are showing up in discovery..

Please share the full config.

9

For discovery.seed_hosts i have used 9300, it show's again same error.

10

Why do the ports i mentioned then show up in the logs you posted?

If you can not share real logs and config I do not think i can help much.

1 Like
11

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