# Elastic master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [January 7, 2020, 7:30pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118 "2020-01-07T19:30:09Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Sreekanth3](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@Sreekanth3](https://discuss.elastic.co/u/Sreekanth3)\ **Post date:** [January 7, 2020, 7:30pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/1 "2020-01-07T19:30:09Z")
Hi , I have upgraded my elasticsearch cluster of 3 nodes from 7.4.0 to 7.5.1 and after completing the upgradation of the ES . I'm getting this error ` master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes` here is my one of the node's configuration cluster.name: JSR node.name: elk-3 network.host: 192.168.1.72 http.port: 9200 transport.tcp.port: 9300 discovery.seed\_hosts: ["192.168.1.59:9300", "192.168.1.62:9300", "192.168.1.72:9300"] cluster.initial\_master\_nodes: ["192.168.1.59:9300","192.168.1.62:9300", "192.168.1.72:9300"] discovery.zen.minimum\_master\_nodes: 2 xpack.license.self\_generated.type: basic xpack.ml.enabled: false Should i add any more to this configuration? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 7, 2020, 8:07pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/2 "2020-01-07T20:07:12Z")
> [@Sreekanth3](#): > > `this node has not previously joined a bootstrapped (v7+) cluster` This node is brand-new and not the result of an upgrade. ---
**Author:** ![Sreekanth3](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@Sreekanth3](https://discuss.elastic.co/u/Sreekanth3)\ **Post date:** [January 7, 2020, 8:10pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/3 "2020-01-07T20:10:10Z")
Hi @DavidTurner `This node is brand-new and not the result of an upgrade` then how can i manage my cluster to elect an master node , before the upgradation it was working well , After the nodes been upgraded to 7.5.1 the problem started. ---
**Author:** ![Sreekanth3](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@Sreekanth3](https://discuss.elastic.co/u/Sreekanth3)\ **Post date:** [January 7, 2020, 8:28pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/4 "2020-01-07T20:28:58Z")
> log [20:28:00.408] [info][licensing][plugins] Imported changed license information from Elasticsearch for the [data] cluster: type: basic | status: active > log [20:28:00.408] [info][licensing][plugins] Imported changed license information from Elasticsearch for the [data] cluster: type: basic | status: active > log [20:29:00.396] [warning][licensing][plugins] License information could not be obtained from Elasticsearch for the [data] cluster. TypeError: Cannot use 'in' operator to search for 'type' in null @DavidTurner these are the kibana logs .... back to back it is importing and can't obtain the license from ES . Two nodes have started and one node is still showing the error of the master not elected. { "error" : { "root\_cause" : [ { "type" : "master\_not\_discovered\_exception", "reason" : null } ], "type" : "master\_not\_discovered\_exception", "reason" : null }, "status" : 503 } This is one of the node's health , the other two are having health green ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 7, 2020, 8:52pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/5 "2020-01-07T20:52:01Z")
If two of the nodes report green health then the master has been elected, so the question is why this other node can't join it. You've only shared the first part of the log message, and the rest of the message is important. ---
**Author:** ![Sreekanth3](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@Sreekanth3](https://discuss.elastic.co/u/Sreekanth3)\ **Post date:** [January 8, 2020, 11:27am UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/6 "2020-01-08T11:27:54Z")
[2020-01-08T14:11:19,019][INFO][o.e.c.c.JoinHelper] [elk-1] failed to join {elk-2}{6cWJvDm8TOaJIhtBQDR9FA}{5Givex09R32BuAOLB9ChGA}{192.168.1.62}{192.168.1.62:9300}{dilm}{mlmory=10317410304, ml.max\_open\_jobs=20, xpack.installed=true} with JoinRequest{sourceNode={elk-1}{WSimmT65Rj26vOT4Jqsy2Q}{H4J-qqnvT3ecJwQXR9\_tCw}{192.168.1.59}{192.168.1.59:9300}{distalled=true}, optionalJoin=Optional.empty} > org.elasticsearch.transport.RemoteTransportException: [elk-2][192.168.1.62:9300][internal:cluster/coordination/join] > Caused by: java.lang.IllegalStateException: failure when sending a validation request to node > at org.elasticsearch.cluster.coordination.Coordinator$2.onFailure(Coordinator.java:513) ~[elasticsearch-7.5.1.jar:7.5.1] > at org.elasticsearch.action.ActionListenerResponseHandler.handleException(ActionListenerResponseHandler.java:59) ~[elasticsearch-7.5.1.jar:7.5.1] > at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1120) ~[elasticsearch-7.5.1.jar:7.5.1] > at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1120) ~[elasticsearch-7.5.1.jar:7.5.1] > at org.elasticsearch.transport.InboundHandler.lambda$handleException$2(InboundHandler.java:243) ~[elasticsearch-7.5.1.jar:7.5.1] > at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:703) ~[elasticsearch-7.5.1.jar:7.5.1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:?] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:?] > at java.lang.Thread.run(Thread.java:748) [?:?] > Caused by: org.elasticsearch.transport.RemoteTransportException: [elk-1][192.168.1.59:9300][internal:cluster/coordination/join/validate] > Caused by: org.elasticsearch.cluster.coordination.CoordinationStateRejectedException: join validation on cluster state with a different cluster uuid fmC6Hhd7TFOlYyCs8shEZw than locuuid qGkJy0s6Th-pFVTlW7yKFg, rejecting > at org.elasticsearch.cluster.coordination.JoinHelper.lambda$new$4(JoinHelper.java:148) ~[elasticsearch-7.5.1.jar:7.5.1] > at org.elasticsearch.xpack.security.transport.SecurityServerTransportInterceptor$ProfileSecuredRequestHandler$1.doRun(SecurityServerTransportInterceptor.java:257) ~[?:?] > at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-7.5.1.jar:7.5.1] > at org.elasticsearch.xpack.security.transport.SecurityServerTransportInterceptor$ProfileSecuredRequestHandler.messageReceived(SecurityServerTransportInterceptor.java:315) ~ > at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:63) ~[elasticsearch-7.5.1.jar:7.5.1] > at org.elasticsearch.transport.InboundHandler$RequestHandler.doRun(InboundHandler.java:264) ~[elasticsearch-7.5.1.jar:7.5.1] > at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:773) ~[elasticsearch-7.5.1.jar:7.5.1] > at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-7.5.1.jar:7.5.1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?] > at java.lang.Thread.run(Thread.java:834) ~[?:?] This is log for the first node which hasn't joined the cluster ---
**Author:** ![Sreekanth3](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@Sreekanth3](https://discuss.elastic.co/u/Sreekanth3)\ **Post date:** [January 8, 2020, 11:31am UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/7 "2020-01-08T11:31:10Z")
failed to validate incoming join request from node [{elk-1}{WSimmT65Rj26vOT4Jqsy2Q}{IXD5y6UxQSyQZ8XGpCFCIQ}{192.168.1.59}{192.168.1.59:9300}{dilm}{ml.machine\_memory=8203743232, ml.max\_open\_jobs=20, xpack.installed=true}] ``` org.elasticsearch.transport.RemoteTransportException: [elk-1][192.168.1.59:9300][internal:cluster/coordination/join/validate]Caused by: org.elasticsearch.cluster.coordination.CoordinationStateRejectedException: join validation on cluster state with a different cluster uuid fmC6Hhd7TFOlYyCs8shEZw than locuuid qGkJy0s6Th-pFVTlW7yKFg, rejecting at org.elasticsearch.cluster.coordination.JoinHelper.lambda$new$4(JoinHelper.java:148) ~[elasticsearch-7.5.1.jar:7.5.1] at org.elasticsearch.xpack.security.transport.SecurityServerTransportInterceptor$ProfileSecuredRequestHandler$1.doRun(SecurityServerTransportInterceptor.java:257) ~[?:?] at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-7.5.1.jar:7.5.1] at org.elasticsearch.xpack.security.transport.SecurityServerTransportInterceptor$ProfileSecuredRequestHandler.messageReceived(SecurityServerTransportInterceptor.java:315) ~ at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:63) ~[elasticsearch-7.5.1.jar:7.5.1] at org.elasticsearch.transport.InboundHandler$RequestHandler.doRun(InboundHandler.java:264) ~[elasticsearch-7.5.1.jar:7.5.1] at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:773) ~[elasticsearch-7.5.1.jar:7.5.1] at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-7.5.1.jar:7.5.1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:1.8.0_181] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:1.8.0_181] at java.lang.Thread.run(Thread.java:834) [?:1.8.0_181] [2020-01-08T15:23:07,800][INFO][o.e.c.m.MetaDataIndexTemplateService] [elk-2] adding template [.management-beats] for index patterns [.management-beats] ``` [2020-01-08T15:29:48,094][INFO][o.e.c.m.MetaDataCreateIndexService] [elk-2] [.kibana\_task\_manager\_3] creating index, cause [api], templates , shards [1]/[1], mappings [\_doc] [2020-01-08T15:29:48,607][INFO][o.e.c.r.a.AllocationService] [elk-2] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.kibana\_task\_manager\_3][0]] This is the log of the other node which is working fine and showing the cluster health as green. ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/5/e50b70b9a2a56e4ad7b01da999d16f477985dd71.png) And check the image once please. > { > "name" : "elk-1", > "cluster\_name" : "JSR", > "cluster\_uuid" : "na", > "version" : { > "number" : "7.5.1", > "build\_flavor" : "default", > "build\_type" : "tar", > "build\_hash" : "3ae9ac9a93c95bd0cdc054951cf95d88e1e18d96", > "build\_date" : "2019-12-16T22:57:37.835892Z", > "build\_snapshot" : false, > "lucene\_version" : "8.3.0", > "minimum\_wire\_compatibility\_version" : "6.8.0", > "minimum\_index\_compatibility\_version" : "6.0.0-beta1" > }, > "tagline" : "You Know, for Search" > } And this is the response i got from the node which is not able to join the cluster and surprisingly it is not showing any UUID . Could you please help me with this . ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 8, 2020, 12:24pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/8 "2020-01-08T12:24:21Z")
> [@Sreekanth3](#): > > `join validation on cluster state with a different cluster uuid fmC6Hhd7TFOlYyCs8shEZw than locuuid qGkJy0s6Th-pFVTlW7yKFg, rejecting` This node used to belong to a different cluster. It is not permitted to move nodes between clusters, as this can result in data loss. ---
**Author:** ![Sreekanth3](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@Sreekanth3](https://discuss.elastic.co/u/Sreekanth3)\ **Post date:** [January 8, 2020, 12:27pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/9 "2020-01-08T12:27:02Z")
That means , the node is lost from the cluster . I can't join them by anymeans ? But previously those are the nodes in my cluster . But 1.59 has changed the UUID and now it is not generating the UUID also . If it is a separate node , it should have some uuid for itself right? ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [January 8, 2020, 3:35pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/10 "2020-01-08T15:35:10Z")
> [@Sreekanth3](#): > > That means , the node is lost from the cluster . I can't join them by anymeans ? I wouldn't say that the node is "lost from the cluster". It apparently never belonged to the same cluster as the other two nodes, because if they were in the same cluster then they would have the same cluster UUID. > [@Sreekanth3](#): > > If it is a separate node , it should have some uuid for itself right? Nodes have a node ID (e.g. `WSimmT65Rj26vOT4Jqsy2Q` in your cluster) but the cluster UUID identifies the whole cluster. ---
**Author:** ![Sreekanth3](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@Sreekanth3](https://discuss.elastic.co/u/Sreekanth3)\ **Post date:** [January 8, 2020, 3:52pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/11 "2020-01-08T15:52:49Z")
Thank you @DavidTurner . ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 5, 2020, 3:55pm UTC](https://discuss.elastic.co/t/elastic-master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/214118/12 "2020-02-05T15:55:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.