Cluster node discovery failed

docker

(Wujiaxin159) #1

elk version: 6.3.0
Using docker container
Server IP: 9.77.10.27 --> Docker IP: 172.17.0.2
Server IP: 9.77.10.28 --> Docker IP: 172.17.0.3

9.77.10.27 config

cluster.name: elk
node.name: node-1
network.host: 0.0.0.0
discovery.zen.ping.unicast.hosts: ["9.77.10.27:9300","9.77.10.28:9300"]
discovery.zen.minimum_master_nodes: 1
node.master: true
node.data: true
transport.tcp.port: 9300

9.77.10.27 config

cluster.name: elk
node.name: node-2
network.host: 0.0.0.0
discovery.zen.ping.unicast.hosts: ["9.77.10.27:9300","9.77.10.28:9300"]
discovery.zen.minimum_master_nodes: 1
node.master: true
node.data: true
transport.tcp.port: 9300

After starting, there is only one node in the clusters of monitoring.


(David Pilato) #2

What are the logs saying? Any kind of firewall that would not expose port 9300?


(Mark Walkom) #3

Also what does your docker config file/command look like?


(Wujiaxin159) #4

Yes, the port is open and can be requested in docker.


(Wujiaxin159) #6

Docker Bridged mode binding host host IP failed, binding container IP causes cluster discovery failure.Just switch to host mode.


(system) #7

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.