# Elastic search 7.0 cluster master node handover problem
**URL:** https://discuss.elastic.co/t/elastic-search-7-0-cluster-master-node-handover-problem/180968
**Category:** Elasticsearch
**Created:** [May 14, 2019, 9:33am UTC](https://discuss.elastic.co/t/elastic-search-7-0-cluster-master-node-handover-problem/180968 "2019-05-14T09:33:32Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@8a2de8f67ab9a7e963a8](https://discuss.elastic.co/u/8a2de8f67ab9a7e963a8)
#### Post date: [May 14, 2019, 9:33am UTC](https://discuss.elastic.co/t/elastic-search-7-0-cluster-master-node-handover-problem/180968/1 "2019-05-14T09:33:32Z")
[2019-05-14T17:29:05,931][WARN][o.e.c.c.ClusterFormationFailureHelper] [node-1-search] master not discovered or elected yet, an election requires a node with id [oTcvvEb8R2G73xLl0U3srQ], have discovered which is not a quorum; discovery will continue using [110.242.49.24:9300] from hosts providers and [{node-2-master}{oTcvvEb8R2G73xLl0U3srQ}{UW5CKZZSRJqZJHdu4\_XqdQ}{110.242.49.24}{110.242.49.24:9300}{ml.machine\_memory=67530166272, ml.max\_open\_jobs=20, xpack.installed=true}, {node-1-search}{Q7fHLH70RiKiYp\_QPKxcgg}{BU0h0J0MTA-zwA7Ka2zPQw}{110.242.49.23}{110.242.49.23:9300}{ml.machine\_memory=67522936832, xpack.installed=true, ml.max\_open\_jobs=20}] from last-known cluster state; node term 5, last-accepted version 191 in term 5
[2019-05-14T17:29:06,144][DEBUG][o.e.a.a.c.n.i.TransportNodesInfoAction] [node-1-search] failed to execute on node [oTcvvEb8R2G73xLl0U3srQ]
org.elasticsearch.transport.NodeNotConnectedException: [node-2-master][110.242.49.24:9300] Node not connected
I tried to stop the node-2-master master master service, but the node-1-search node did not take over.
---
### Author:  [@8a2de8f67ab9a7e963a8](https://discuss.elastic.co/u/8a2de8f67ab9a7e963a8)
#### Post date: [May 14, 2019, 9:34am UTC](https://discuss.elastic.co/t/elastic-search-7-0-cluster-master-node-handover-problem/180968/2 "2019-05-14T09:34:53Z")
cluster.name: qiniu-ELK
node.name: node-2-master
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: 110.242.49.24
http.port: 9200
discovery.seed\_hosts: ["110.242.49.23","110.242.49.24"]
cluster.initial\_master\_nodes: ["110.242.49.23", "110.242.49.24"]
gateway.recover\_after\_nodes: 1
indices.query.bool.max\_clause\_count: 8192
search.max\_buckets: 100000
discovery.zen.minimum\_master\_nodes: 1
main node configuration
---
### Author:  [@8a2de8f67ab9a7e963a8](https://discuss.elastic.co/u/8a2de8f67ab9a7e963a8)
#### Post date: [May 14, 2019, 9:35am UTC](https://discuss.elastic.co/t/elastic-search-7-0-cluster-master-node-handover-problem/180968/3 "2019-05-14T09:35:26Z")
cluster.name: qiniu-ELK
node.name: node-1-search
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
network.host: 110.242.49.23
http.port: 9200
discovery.seed\_hosts: ["110.242.49.23", "110.242.49.24"]
cluster.initial\_master\_nodes: ["110.242.49.23", "110.242.49.24"]
gateway.recover\_after\_nodes: 1
indices.query.bool.max\_clause\_count: 8192
search.max\_buckets: 100000
discovery.zen.minimum\_master\_nodes: 1
data node configuration
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [May 14, 2019, 10:15am UTC](https://discuss.elastic.co/t/elastic-search-7-0-cluster-master-node-handover-problem/180968/4 "2019-05-14T10:15:10Z")
> [@8a2de8f67ab9a7e963a8](#):
>
> `discovery.zen.minimum_master_nodes: 1`
This setting is ignored in version 7, but if you were using this setting in an earlier version in a cluster with 2 master-eligible nodes then you were at serious risk of data loss.
This [blog post](https://www.elastic.co/blog/a-new-era-for-cluster-coordination-in-elasticsearch) has more details about the changes in version 7, specifically:
> It is also safe to remove nodes simply by stopping them **as long as you do not stop half or more of the master-eligible nodes all at once**.
In this case, you have removed half of the master-eligible nodes all at once (i.e. one of the two nodes) so the remaining node does not form a majority.
---
### Author:  [@8a2de8f67ab9a7e963a8](https://discuss.elastic.co/u/8a2de8f67ab9a7e963a8)
#### Post date: [May 14, 2019, 10:18am UTC](https://discuss.elastic.co/t/elastic-search-7-0-cluster-master-node-handover-problem/180968/5 "2019-05-14T10:18:02Z")
Hello
You mean I need more than three, don't you?
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [May 14, 2019, 10:20am UTC](https://discuss.elastic.co/t/elastic-search-7-0-cluster-master-node-handover-problem/180968/6 "2019-05-14T10:20:24Z")
If you want the cluster to carry on working even if you shut down one of the nodes then you need at least three master-eligible nodes.
---
### Author:  [@8a2de8f67ab9a7e963a8](https://discuss.elastic.co/u/8a2de8f67ab9a7e963a8)
#### Post date: [May 14, 2019, 11:01am UTC](https://discuss.elastic.co/t/elastic-search-7-0-cluster-master-node-handover-problem/180968/7 "2019-05-14T11:01:54Z")
Okay, thank you.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 11, 2019, 11:02am UTC](https://discuss.elastic.co/t/elastic-search-7-0-cluster-master-node-handover-problem/180968/8 "2019-06-11T11:02:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.