# Can not create elasticsearch cluster in different servers with docker compose
**URL:** https://discuss.elastic.co/t/can-not-create-elasticsearch-cluster-in-different-servers-with-docker-compose/223896
**Category:** Elasticsearch
**Tags:** docker
**Created:** [March 17, 2020, 10:13am UTC](https://discuss.elastic.co/t/can-not-create-elasticsearch-cluster-in-different-servers-with-docker-compose/223896 "2020-03-17T10:13:53Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@wvx](https://discuss.elastic.co/u/wvx)
#### Post date: [March 17, 2020, 10:13am UTC](https://discuss.elastic.co/t/can-not-create-elasticsearch-cluster-in-different-servers-with-docker-compose/223896/1 "2020-03-17T10:13:53Z")
I have 2 servers, and create elasticsearch nodes in the 2 servers. the content of docker-compose.yml files are like these:
```auto
es0:
image: elasticsearch:7.6.0
container_name: es0
environment:
- "ES_JAVA_OPTS=-Xms1024m -Xmx1024m"
ulimits:
memlock:
soft: -1
hard: -1
ports:
- 9200:9200
- 9300:9300
volumes:
- "/mnt/docker/es0/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml"
- "/mnt/docker/es0/data:/usr/share/elasticsearch/data"
- "/mnt/docker/es0/plugins:/usr/share/elasticsearch/plugins"
- "/mnt/docker/es0/config/cert:/usr/share/elasticsearch/config/cert"
```
```auto
es1:
image: elasticsearch:7.6.0
container_name: es1
environment:
- "ES_JAVA_OPTS=-Xms1024m -Xmx1024m"
ulimits:
memlock:
soft: -1
hard: -1
ports:
- 9200:9200
- 9300:9300
volumes:
- "/mnt/docker/es1/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml"
- "/mnt/docker/es1/data:/usr/share/elasticsearch/data"
- "/mnt/docker/es1/plugins:/usr/share/elasticsearch/plugins"
- "/mnt/docker/es1/config/cert:/usr/share/elasticsearch/config/cert"
```
and I configured the elasticsearch.yml like these:
```auto
cluster.name: hs-cluster
node.name: es-00
node.master: true
node.data: true
http.host: 0.0.0.0
http.port: 9200
transport.host: 0.0.0.0
transport.tcp.port: 9300
#network.host: 0.0.0.0
network.bind_host: ["192.168.0.2", "101.xx.xx.136"]
network.publish_host: 192.168.0.2
gateway.recover_after_nodes: 1
http.cors.enabled: true
http.cors.allow-origin: "*"
cluster.initial_master_nodes: ["es-00", "es-01"]
discovery.seed_hosts: ["192.168.0.2:9300", "192.168.0.3:9300"]
bootstrap.memory_lock: true
bootstrap.system_call_filter: false
```
```auto
cluster.name: hs-cluster
node.name: es-01
node.master: true
node.data: true
http.host: 0.0.0.0
http.port: 9200
transport.host: 0.0.0.0
transport.tcp.port: 9300
#network.host: 0.0.0.0
network.bind_host: ["192.168.0.3", "101.xx.xx.137"]
network.publish_host: 192.168.0.3
gateway.recover_after_nodes: 1
http.cors.enabled: true
http.cors.allow-origin: "*"
cluster.initial_master_nodes: ["es-00", "es-01"]
discovery.seed_hosts: ["192.168.0.2:9300", "192.168.0.3:9300"]
bootstrap.memory_lock: true
bootstrap.system_call_filter: false
```
when I run the instances, they all started successfully. But when I call \_cluster/state?pretty, they all gave the error message:
```auto
{
"error" : {
"root_cause" : [
{
"type" : "master_not_discovered_exception",
"reason" : null
}
],
"type" : "master_not_discovered_exception",
"reason" : null
},
"status" : 503
}
```
that means they can't find each other. I also tried to set _`network.host: 0.0.0.0`_ but the result was the same. Who know the reason of this master not discovered exception? How to resolve it?
btw, I can ran the cluster in the same server with docker compose. But in different servers, it is failed. I also ran telnet xxx 9300 in each server, they all connected.
And I add networks to docker-compose.yml,
and change network configuration in elasticsearch.yml:
network.host: 0.0.0.0
network.publish\_host: 192.168.0.2
and restart instances again. Then I got the error message like this:
> master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and this node must discover master-eligible nodes [es-00, es-01] to bootstrap a cluster:
> have discovered [{es-00}{0laFYaAxRr22MfbxvFZSlw}{tEDB7BzSQ2am1L30XTTcBQ}{172.20.0.2}{172.20.0.2:9300}{dilm}{ml.machine\_memory=8201236480, xpack.installed=true, ml.max\_open\_jobs=20}];
> discovery will continue using [192.168.0.2:9300, 192.168.0.3:9300] from hosts providers
> and [{es-00}{0laFYaAxRr22MfbxvFZSlw}{tEDB7BzSQ2am1L30XTTcBQ}{172.20.0.2}{172.20.0.2:9300}{dilm}{ml.machine\_memory=8201236480, xpack.installed=true, ml.max\_open\_jobs=20}]
> from last-known cluster state; node term 0, last-accepted version 0 in term 0
---
### Author:  [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [March 17, 2020, 10:26am UTC](https://discuss.elastic.co/t/can-not-create-elasticsearch-cluster-in-different-servers-with-docker-compose/223896/2 "2020-03-17T10:26:35Z")
> [@wvx](#):
>
> `... have discovered [{es-00}{0laFYaAxRr22MfbxvFZSlw}{tEDB7BzSQ2am1L30XTTcBQ}{172.20.0.2}{172.20.0.2:9300}{dilm}{ml.machine_memory=8201236480, xpack.installed=true, ml.max_open_jobs=20}]; discovery will continue using [192.168.0.2:9300, 192.168.0.3:9300] ...`
Your nodes have addresses like `172.20.0.2` but you are trying to discover them at addresses like `192.168.0.2`? That seems unlikely to work.
You almost certainly don't want to set `network.publish_host`, but maybe you want `network.host: 192.168.0.2` or `network.host: _eth0_` or whatever the interface is called?
---
### Author:  [@wvx](https://discuss.elastic.co/u/wvx)
#### Post date: [March 19, 2020, 2:45am UTC](https://discuss.elastic.co/t/can-not-create-elasticsearch-cluster-in-different-servers-with-docker-compose/223896/3 "2020-03-19T02:45:01Z")
I see. It's the network problem.
I created the es cluster with network-mode: host in docker-compose. It is said host mode is not good in production server.
I will try to use k8s to create es cluster. Thank you very much!
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 16, 2020, 2:45am UTC](https://discuss.elastic.co/t/can-not-create-elasticsearch-cluster-in-different-servers-with-docker-compose/223896/4 "2020-04-16T02:45:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.