# 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:** [July 3, 2019, 12:37pm UTC](https://discuss.elastic.co/t/master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/188706 "2019-07-03T12:37:50Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![gowsalai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gowsalai/32/46074_2.png) [@gowsalai](https://discuss.elastic.co/u/gowsalai)\ **Post date:** [July 3, 2019, 12:37pm UTC](https://discuss.elastic.co/t/master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/188706/1 "2019-07-03T12:37:50Z")
Hi, We are getting the below error during eck operator ([https://www.elastic.co/guide/en/cloud-on-k8s/0.8/k8s-quickstart.html](https://www.elastic.co/guide/en/cloud-on-k8s/0.8/k8s-quickstart.html)) bring up with persistent volume. We don't see the issue without the persistent volume. bootstrapping the cluster seems to be a problem. {"type": "server", "timestamp": "2019-07-03T12:24:37,124+0000", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "cluster.name": "quickstart", "node.name": "quickstart-es-2qfgzkkzvs", "message": "master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [quickstart-es-2qfgzkkzvs, quickstart-es-2wpr5mhtmj, quickstart-es-z7ds4z8shm] to bootstrap a cluster: have discovered [{quickstart-es-5tf6ztjt66}{2qdfsRUnT\_KssSSeV4GVAg}{6uye\_N2LR-6mh5wXf\_E6qQ}{10.2.0.23}{10.2.0.23:9300}{ml.machine\_memory=2147483648, ml.max\_open\_jobs=20, xpack.installed=true}, {quickstart-es-dlw4d4kkl5}{EPiU72QARzK2FIOjEHfmwQ}{WTbw\_jfLRuuoTyiGSaH9OQ}{10.2.3.148}{10.2.3.148:9300}{ml.machine\_memory=2147483648, ml.max\_open\_jobs=20, xpack.installed=true}]; discovery will continue using [127.0.0.1:9300, 127.0.0.1:9301, 127.0.0.1:9302, 127.0.0.1:9303, 127.0.0.1:9304, 10.2.0.23:9300, 10.2.3.148:9300] from hosts providers and [{quickstart-es-2qfgzkkzvs}{qVsmhSygRXSRZ\_Wjfjyqfg}{pETjBPitSBSHjQbyrR1skg}{10.2.1.110}{10.2.1.110:9300}{ml.machine\_memory=2147483648, xpack.installed=true, ml.max\_open\_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0" } not able to specify the node name or cluster.initial\_master\_nodes because the admission webhook doesn't allow them to be user specified. Error from server (node[0]: cluster.initial\_master\_nodes, node.name is not user configurable): error when creating "es\_cl\_pv.yaml": admission webhook "[validation.elasticsearch.elastic.co](http://validation.elasticsearch.elastic.co)" denied the request: node[0]: cluster.initial\_master\_nodes, node.name is not user configurable ---
**Author:** ![gowsalai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gowsalai/32/46074_2.png) [@gowsalai](https://discuss.elastic.co/u/gowsalai)\ **Post date:** [July 4, 2019, 10:08am UTC](https://discuss.elastic.co/t/master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/188706/2 "2019-07-04T10:08:19Z")
Seems like the problem is when we try to have more than one master eligible node. Following is the yaml file used to create the cluster. apiVersion: [elasticsearch.k8s.elastic.co/v1alpha1](http://elasticsearch.k8s.elastic.co/v1alpha1) kind: Elasticsearch metadata: name: eck namespace: elastic-system spec: version: 7.1.0 nodes: - nodeCount: 5 config: # node.name: ${HOSTNAME} ``` node.master: true node.data: true node.ingest: true podTemplate: spec: containers: - name: elasticsearch resources: limits: memory: 25Gi cpu: 4000m volumeClaimTemplates: - metadata: name: data spec: accessModes: - ReadWriteOnce storageClassName: rook-block resources: requests: storage: 150Gi ``` When tried creating single master node and mutiple data / ingest nodes the problem is not seen. But our requirement is having minimum of 3 master nodes. ---
**Author:** ![gowsalai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gowsalai/32/46074_2.png) [@gowsalai](https://discuss.elastic.co/u/gowsalai)\ **Post date:** [July 8, 2019, 5:35am UTC](https://discuss.elastic.co/t/master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/188706/3 "2019-07-08T05:35:06Z")
Hi, Can you please share the details about how to configure the multi master node elastic cluster in ECK operator?. Thanks, Gowsalai ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 5, 2019, 5:35am UTC](https://discuss.elastic.co/t/master-not-discovered-yet-this-node-has-not-previously-joined-a-bootstrapped-v7-cluster-and-this-node-must-discover-master-eligible-nodes/188706/4 "2019-08-05T05:35:15Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.