# Cluster (connect 2 nodes) **URL:** \ **Category:** Elasticsearch\ **Created:** [June 4, 2018, 8:11am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384 "2018-06-04T08:11:35Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\ **Post date:** [June 4, 2018, 10:17am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/21 "2018-06-04T10:17:29Z")
```auto [root@frghcslnetv12 data]# tail /var/log/elasticsearch/network-logs.log [2018-06-04T12:15:42,440][INFO][o.e.d.z.ZenDiscovery] [9hSWSDU] failed to send join request to master [{network-1}{M3r-tbp1QuqOQSj5UM6Ehw}{MdvaRbsfRty_dAHM8jKmkQ}{172.16.250.29}{172.16.250.29:9300}], reason [RemoteTransportException[[network-1][172.16.250.29:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[9hSWSDU][172.16.250.30:9300] connect_exception]; nested: IOException[No route to host: 172.16.250.30/172.16.250.30:9300]; nested: IOException[No route to host]; ] [2018-06-04T12:15:45,466][INFO][o.e.d.z.ZenDiscovery] [9hSWSDU] failed to send join request to master [{network-1}{M3r-tbp1QuqOQSj5UM6Ehw}{MdvaRbsfRty_dAHM8jKmkQ}{172.16.250.29}{172.16.250.29:9300}], reason [RemoteTransportException[[network-1][172.16.250.29:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[9hSWSDU][172.16.250.30:9300] connect_exception]; nested: IOException[No route to host: 172.16.250.30/172.16.250.30:9300]; nested: IOException[No route to host]; ] [2018-06-04T12:15:48,495][INFO][o.e.d.z.ZenDiscovery] [9hSWSDU] failed to send join request to master [{network-1}{M3r-tbp1QuqOQSj5UM6Ehw}{MdvaRbsfRty_dAHM8jKmkQ}{172.16.250.29}{172.16.250.29:9300}], reason [RemoteTransportException[[network-1][172.16.250.29:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[9hSWSDU][172.16.250.30:9300] connect_exception]; nested: IOException[No route to host: 172.16.250.30/172.16.250.30:9300]; nested: IOException[No route to host]; ] [2018-06-04T12:16:06,535][INFO][o.e.d.z.ZenDiscovery] [9hSWSDU] failed to send join request to master [{network-1}{M3r-tbp1QuqOQSj5UM6Ehw}{MdvaRbsfRty_dAHM8jKmkQ}{172.16.250.29}{172.16.250.29:9300}], reason [RemoteTransportException[[network-1][172.16.250.29:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[9hSWSDU][172.16.250.30:9300] connect_exception]; nested: IOException[No route to host: 172.16.250.30/172.16.250.30:9300]; nested: IOException[No route to host]; ] [2018-06-04T12:16:10,549][INFO][o.e.d.z.ZenDiscovery] [9hSWSDU] failed to send join request to master [{network-1}{M3r-tbp1QuqOQSj5UM6Ehw}{MdvaRbsfRty_dAHM8jKmkQ}{172.16.250.29}{172.16.250.29:9300}], reason [RemoteTransportException[[network-1][172.16.250.29:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[9hSWSDU][172.16.250.30:9300] connect_exception]; nested: IOException[No route to host: 172.16.250.30/172.16.250.30:9300]; nested: IOException[No route to host]; ] [2018-06-04T12:16:13,556][INFO][o.e.d.z.ZenDiscovery] [9hSWSDU] failed to send join request to master [{network-1}{M3r-tbp1QuqOQSj5UM6Ehw}{MdvaRbsfRty_dAHM8jKmkQ}{172.16.250.29}{172.16.250.29:9300}], reason [RemoteTransportException[[network-1][172.16.250.29:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[9hSWSDU][172.16.250.30:9300] connect_exception]; nested: IOException[No route to host: 172.16.250.30/172.16.250.30:9300]; nested: IOException[No route to host]; ] [2018-06-04T12:16:17,638][INFO][o.e.d.z.ZenDiscovery] [9hSWSDU] failed to send join request to master [{network-1}{M3r-tbp1QuqOQSj5UM6Ehw}{MdvaRbsfRty_dAHM8jKmkQ}{172.16.250.29}{172.16.250.29:9300}], reason [RemoteTransportException[[network-1][172.16.250.29:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[9hSWSDU][172.16.250.30:9300] connect_exception]; nested: IOException[No route to host: 172.16.250.30/172.16.250.30:9300]; nested: IOException[No route to host]; ] [2018-06-04T12:16:27,675][INFO][o.e.d.z.ZenDiscovery] [9hSWSDU] failed to send join request to master [{network-1}{M3r-tbp1QuqOQSj5UM6Ehw}{MdvaRbsfRty_dAHM8jKmkQ}{172.16.250.29}{172.16.250.29:9300}], reason [RemoteTransportException[[network-1][172.16.250.29:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[9hSWSDU][172.16.250.30:9300] connect_exception]; nested: IOException[No route to host: 172.16.250.30/172.16.250.30:9300]; nested: IOException[No route to host]; ] [2018-06-04T12:16:31,688][INFO][o.e.d.z.ZenDiscovery] [9hSWSDU] failed to send join request to master [{network-1}{M3r-tbp1QuqOQSj5UM6Ehw}{MdvaRbsfRty_dAHM8jKmkQ}{172.16.250.29}{172.16.250.29:9300}], reason [RemoteTransportException[[network-1][172.16.250.29:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[9hSWSDU][172.16.250.30:9300] connect_exception]; nested: IOException[No route to host: 172.16.250.30/172.16.250.30:9300]; nested: IOException[No route to host]; ] [2018-06-04T12:16:49,729][INFO][o.e.d.z.ZenDiscovery] [9hSWSDU] failed to send join request to master [{network-1}{M3r-tbp1QuqOQSj5UM6Ehw}{MdvaRbsfRty_dAHM8jKmkQ}{172.16.250.29}{172.16.250.29:9300}], reason [RemoteTransportException[[network-1][172.16.250.29:9300][internal:discovery/zen/join]]; nested: ConnectTransportException[[9hSWSDU][172.16.250.30:9300] connect_exception]; nested: IOException[No route to host: 172.16.250.30/172.16.250.30:9300]; nested: IOException[No route to host]; ] ``` ---
**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\ **Post date:** [June 4, 2018, 10:18am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/22 "2018-06-04T10:18:41Z")
Are the two hosts on the same network, is the a firewall between them? ``` ifconfig ``` Are there any iptables rules? ``` iptables -nvL ``` ---
**Author:** ![Hamza\_Dhahri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hamza_dhahri/32/29968_2.png) [@Hamza\_Dhahri](https://discuss.elastic.co/u/Hamza_Dhahri)\ **Post date:** [June 4, 2018, 10:19am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/23 "2018-06-04T10:19:47Z")
hi jamesspi i am facing problem in elasticsearch could you help me please? ---
**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\ **Post date:** [June 4, 2018, 10:20am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/24 "2018-06-04T10:20:29Z")
> [@jamesspi](#): > > ifconfig They are on the same network : ```auto [root@frghcslnetv12 ~]# ifconfig eth0: flags=4163 mtu 1500 inet 172.16.250.30 netmask 255.255.255.0 broadcast 172.16.250.255 inet6 fe80::250:56ff:feb6:71fd prefixlen 64 scopeid 0x20 ether 00:50:56:b6:71:fd txqueuelen 1000 (Ethernet) RX packets 38865 bytes 33083427 (31.5 MiB) RX errors 0 dropped 761 overruns 0 frame 0 TX packets 10069 bytes 1607764 (1.5 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1 (Local Loopback) RX packets 5860 bytes 508660 (496.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5860 bytes 508660 (496.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 virbr0: flags=4099 mtu 1500 ether 52:54:00:94:2b:d4 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` ```auto [root@frghcslnetv12 ~]# iptables -nvL Chain INPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 4262 1153K ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 65 4624 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 2449 147K INPUT_direct all -- * * 0.0.0.0/0 0.0.0.0/0 2449 147K INPUT_ZONES_SOURCE all -- * * 0.0.0.0/0 0.0.0.0/0 2449 147K INPUT_ZONES all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 ctstate INVALID 2449 147K REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 0 0 FORWARD_direct all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 FORWARD_IN_ZONES_SOURCE all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 FORWARD_IN_ZONES all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 FORWARD_OUT_ZONES_SOURCE all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 FORWARD_OUT_ZONES all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 ctstate INVALID 0 0 REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT 5084 packets, 693K bytes) pkts bytes target prot opt in out source destination 5084 693K OUTPUT_direct all -- * * 0.0.0.0/0 0.0.0.0/0 Chain FORWARD_IN_ZONES (1 references) pkts bytes target prot opt in out source destination 0 0 FWDI_public all -- eth0 * 0.0.0.0/0 0.0.0.0/0 [goto] 0 0 FWDI_public all -- + * 0.0.0.0/0 0.0.0.0/0 [goto] Chain FORWARD_IN_ZONES_SOURCE (1 references) pkts bytes target prot opt in out source destination Chain FORWARD_OUT_ZONES (1 references) pkts bytes target prot opt in out source destination 0 0 FWDO_public all -- * eth0 0.0.0.0/0 0.0.0.0/0 [goto] 0 0 FWDO_public all -- * + 0.0.0.0/0 0.0.0.0/0 [goto] Chain FORWARD_OUT_ZONES_SOURCE (1 references) pkts bytes target prot opt in out source destination Chain FORWARD_direct (1 references) pkts bytes target prot opt in out source destination Chain FWDI_public (2 references) pkts bytes target prot opt in out source destination 0 0 FWDI_public_log all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 FWDI_public_deny all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 FWDI_public_allow all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 Chain FWDI_public_allow (1 references) pkts bytes target prot opt in out source destination Chain FWDI_public_deny (1 references) pkts bytes target prot opt in out source destination Chain FWDI_public_log (1 references) pkts bytes target prot opt in out source destination Chain FWDO_public (2 references) pkts bytes target prot opt in out source destination 0 0 FWDO_public_log all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 FWDO_public_deny all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 FWDO_public_allow all -- * * 0.0.0.0/0 0.0.0.0/0 Chain FWDO_public_allow (1 references) pkts bytes target prot opt in out source destination Chain FWDO_public_deny (1 references) pkts bytes target prot opt in out source destination Chain FWDO_public_log (1 references) pkts bytes target prot opt in out source destination Chain INPUT_ZONES (1 references) pkts bytes target prot opt in out source destination 2449 147K IN_public all -- eth0 * 0.0.0.0/0 0.0.0.0/0 [goto] 0 0 IN_public all -- + * 0.0.0.0/0 0.0.0.0/0 [goto] Chain INPUT_ZONES_SOURCE (1 references) pkts bytes target prot opt in out source destination Chain INPUT_direct (1 references) pkts bytes target prot opt in out source destination Chain IN_public (2 references) pkts bytes target prot opt in out source destination 2449 147K IN_public_log all -- * * 0.0.0.0/0 0.0.0.0/0 2449 147K IN_public_deny all -- * * 0.0.0.0/0 0.0.0.0/0 2449 147K IN_public_allow all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 ... etc ``` ---
**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\ **Post date:** [June 4, 2018, 10:23am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/25 "2018-06-04T10:23:23Z")
> [@jamesspi](#): > > Are the two hosts on the same network, is the a firewall between them? The node 1 is on : 172.16.250.29 The node 2 is on : 172.16.250.30 ---
**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\ **Post date:** [June 4, 2018, 11:33am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/26 "2018-06-04T11:33:57Z")
@asalma, which is the node giving you issues? .29 or .30? Also, based on your iptables output, I am assuming you are using firewalld? If so, can you run: ``` firewall-cmd --get-active-zones ``` ---
**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\ **Post date:** [June 4, 2018, 11:34am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/27 "2018-06-04T11:34:25Z")
@Hamza_Dhahri, just open a new topic with your question, someone will pick it up 🙂 ---
**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\ **Post date:** [June 4, 2018, 11:35am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/28 "2018-06-04T11:35:09Z")
The ".30" ```auto [root@frghcslnetv12 ~]# firewall-cmd --get-active-zones public interfaces: eth0 ``` ---
**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\ **Post date:** [June 4, 2018, 11:39am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/29 "2018-06-04T11:39:48Z")
Ok, on both nodes, please add: ``` firewall-cmd --zone=public --add-port=9200/tcp --permanent firewall-cmd --zone=public --add-port=9300/tcp --permanent firewall-cmd --reload ``` Restart elasticsearch and try again. ---
**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\ **Post date:** [June 4, 2018, 11:42am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/30 "2018-06-04T11:42:56Z")
> [@jamesspi](#): > > firewall-cmd --zone=public --add-port=9200/tcp --permanent I could do this on : ".30" but on the ".29" I got this : ```auto [root@frghcslnetv10 ~]# firewall-cmd --get-active-zones FirewallD is not running [root@frghcslnetv10 ~]# firewall-cmd --zone=public --add-port=9200/tcp --permanent FirewallD is not running ``` ---
**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\ **Post date:** [June 4, 2018, 11:44am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/31 "2018-06-04T11:44:00Z")
Interesting! Can you run `iptables -nvL` on .29? ---
**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\ **Post date:** [June 4, 2018, 11:44am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/32 "2018-06-04T11:44:01Z")
It workes 🙂 ```auto [root@frghcslnetv12 ~]# curl http://localhost:9200/_cat/nodes?pretty 172.16.250.30 53 98 4 1.28 0.55 0.24 mdi - network-2 172.16.250.29 73 98 98 7.66 8.35 8.30 mdi * network-1 ``` ---
**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\ **Post date:** [June 4, 2018, 11:44am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/33 "2018-06-04T11:44:45Z")
> [@jamesspi](#): > > Can you run `iptables -nvL` on .29? ```auto [root@frghcslnetv10 ~]# iptables -nvL Chain INPUT (policy ACCEPT 1 packets, 73 bytes) pkts bytes target prot opt in out source destination Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination ``` ---
**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\ **Post date:** [June 4, 2018, 11:45am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/34 "2018-06-04T11:45:17Z")
Great! You had a local firewall on .30, but not .29. ---
**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\ **Post date:** [June 4, 2018, 11:45am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/35 "2018-06-04T11:45:50Z")
Thank you a lot @jamesspi ---
**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\ **Post date:** [June 4, 2018, 11:47am UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/36 "2018-06-04T11:47:26Z")
You're welcome! Please close the topic if you're ready 🙂 ---
**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\ **Post date:** [June 4, 2018, 12:04pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/37 "2018-06-04T12:04:24Z")
Please one last question : How can I know that this worked, how can I see this on kibana ? My kibana and logstash are on : ".29" ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/e/7e97d8a869832f78871288417636256e07c024d2.png) Why i can't see the "network-2" ---
**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\ **Post date:** [June 4, 2018, 12:24pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/38 "2018-06-04T12:24:00Z")
Hey @asalma, You can run: ``` GET _cat/nodes?v ``` Or, even better, install the free version of x-pack to get monitoring set up (you can monitor all aspects of the cluster visually, very very helpful) ---
**Author:** ![asalma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/asalma/32/32199_2.png) [@asalma](https://discuss.elastic.co/u/asalma)\ **Post date:** [June 4, 2018, 12:25pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/39 "2018-06-04T12:25:01Z")
> [@jamesspi](#): > > GET \_cat/nodes?v ```auto ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name 172.16.250.29 59 98 93 8.15 7.88 6.64 mdi * network-1 ``` The cluster can't work without the X-pack ? ---
**Author:** ![jamesspi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jamesspi/32/24479_2.png) [@jamesspi](https://discuss.elastic.co/u/jamesspi)\ **Post date:** [June 4, 2018, 12:27pm UTC](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384/40 "2018-06-04T12:27:59Z")
Yes, it can work of course. You should have both nodes listed there if it is still working from before..is elasticsearch still running on .30? [Previous page](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384.md?page=1) [Next page](https://discuss.elastic.co/t/cluster-connect-2-nodes/134384.md?page=3)