# Cluster not forming
**URL:** https://discuss.elastic.co/t/cluster-not-forming/249948
**Category:** Elasticsearch
**Created:** [September 25, 2020, 9:53am UTC](https://discuss.elastic.co/t/cluster-not-forming/249948 "2020-09-25T09:53:43Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@ggrocott](https://discuss.elastic.co/u/ggrocott)
#### Post date: [September 25, 2020, 9:53am UTC](https://discuss.elastic.co/t/cluster-not-forming/249948/1 "2020-09-25T09:53:43Z")
I have two servers, both Ubuntu servers running 20.04.1 and Java versions 11.0.8
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal
root@ip-172-26-9-196:/etc/elasticsearch# java -version
openjdk version "11.0.8" 2020-07-14
OpenJDK Runtime Environment (build 11.0.8+10-post-Ubuntu-0ubuntu120.04)
OpenJDK 64-Bit Server VM (build 11.0.8+10-post-Ubuntu-0ubuntu120.04, mixed mode, sharing)
# I have set up the following on both nodes.
#
cluster.name: cert-elastic
#
#
node.name: cert-es
#
#define node 1 as master-eligible:
node.master: true
#define nodes 2 and 3 as data nodes:
node.data: true
#
#
network.host: 172.26.9.196
#
http.port: 9200
#
transport.host: 172.26.9.196
transport.tcp.port: 9300
transport.publish\_port: 9300
#
discovery.seed\_hosts: ["172.26.9.196", "172.26.10.149"]
#
#
cluster.initial\_master\_nodes: ["cert-es", "cert-es2"]
#
#discovery.zen.ping.unicast.hosts: ["172.26.5.82", "172.26.9.196"]
#
gateway.recover\_after\_nodes: 1
#
* * *
#
cluster.name: cert-elastic
#
#
node.name: cert-es2
#
#define node 1 as master-eligible:
node.master: true
#define nodes 2 and 3 as data nodes:
node.data: true
#
#
network.host: 172.26.10.149
#
http.port: 9200
#
transport.host: 172.26.9.196
transport.tcp.port: 9300
transport.publish\_port: 9300
#
discovery.seed\_hosts: ["172.26.9.196", "172.26.10.149"]
#
#
cluster.initial\_master\_nodes: ["cert-es", "cert-es2"]
#
#discovery.zen.ping.unicast.hosts: ["172.26.5.82", "172.26.9.196"]
#
gateway.recover\_after\_nodes: 1
#
The issue is, when I run the command:
curl -XGET [http://172.26.10.149:9200/\_cluster/health?pretty](http://172.26.10.149:9200/_cluster/health?pretty)
{
"cluster\_name" : "cert-elastic",
"status" : "green",
"timed\_out" : false,
"number\_of\_nodes" : 1,
"number\_of\_data\_nodes" : 1,
"active\_primary\_shards" : 0,
"active\_shards" : 0,
"relocating\_shards" : 0,
"initializing\_shards" : 0,
"unassigned\_shards" : 0,
"delayed\_unassigned\_shards" : 0,
"number\_of\_pending\_tasks" : 0,
"number\_of\_in\_flight\_fetch" : 0,
"task\_max\_waiting\_in\_queue\_millis" : 0,
"active\_shards\_percent\_as\_number" : 100.0
curl -XGET [http://172.26.9.196:9200/\_cl](http://172.26.9.196:9200/_cl) uster/health?pretty
{
"cluster\_name" : "cert-elastic",
"status" : "green",
"timed\_out" : false,
"number\_of\_nodes" : 1,
"number\_of\_data\_nodes" : 1,
"active\_primary\_shards" : 0,
"active\_shards" : 0,
"relocating\_shards" : 0,
"initializing\_shards" : 0,
"unassigned\_shards" : 0,
"delayed\_unassigned\_shards" : 0,
"number\_of\_pending\_tasks" : 0,
"number\_of\_in\_flight\_fetch" : 0,
"task\_max\_waiting\_in\_queue\_millis" : 0,
"active\_shards\_percent\_as\_number" : 100.0
}
The two dont seem to see each other
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [September 25, 2020, 10:01am UTC](https://discuss.elastic.co/t/cluster-not-forming/249948/2 "2020-09-25T10:01:42Z")
Your transport.host on the second node is incorrect.
---
### Author:  [@ggrocott](https://discuss.elastic.co/u/ggrocott)
#### Post date: [September 25, 2020, 10:23am UTC](https://discuss.elastic.co/t/cluster-not-forming/249948/3 "2020-09-25T10:23:12Z")
Yes, that was a typo on my part. The correct Transport address is there.
network.host: 172.26.10.149
http.port: 9200
transport.host: 172.26.10.149
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 23, 2020, 10:23am UTC](https://discuss.elastic.co/t/cluster-not-forming/249948/4 "2020-10-23T10:23:13Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.