I've been playing with Elasticsearch and had a working cluster in a multicast environment using VMs. I recently tried adapting that to work within Docker and I'm running into a wall with the unicast configuration.
Current setup is two nodes: one on the host and another in a docker container (dockerfile/elasticsearch) I'm running the container with: $ docker run -d -h "elasticsearch-node-01" --name="elasticsearch-node-01" \ -p 9201:9200 -p 9301:9300 -v \ /etc/elasticsearch/cluster/:/data \ dockerfile/elasticsearch /elasticsearch/bin/elasticsearch \ -Des.config=/data/elasticsearch.yml It spins up on the docker0 bridge with some IP, 172.17.0.xx docker0 is bound to 172.17.42.1 127.0.0.1 refers to the host in this example I can access the elasticsearch node in the container with any of the commands: $ curl 127.0.0.1:9201 $ curl 172.17.42.1:9201 $ curl 172.17.0.xx:9200 But when I add it to a cluster via unicast, I see an exception thrown with "No route to host" being the reason. After trying a few different IPs to see which could be accessed through the bridge, it seems that the container doesn't know how to speak to the host to join the host node's cluster or tell the host node that it has a cluster that can be joined. The host node logs also shows a similar error: [2014-07-10 12:00:37,264][INFO][discovery.zen] [elasticsearch-node-test] failed to send join request to master [[elasticsearch-node-01][I3LiEOyeSome3djzr37uuQ][elasticsearch-node-01][inet[/172.17.0.14:9300]]], reason [org.elasticsearch.transport.RemoteTransportException: [elasticsearch-node-01][inet[/172.17.0.14:9300]][discovery/zen/join]; org.elasticsearch.transport.ConnectTransportException: [elasticsearch-node-test][inet[/128.59.222.215:9300]] connect_timeout[30s]; java.net.NoRouteToHostException: No route to host] There are two conversations I've found here with docker, elasticsearch and unicast but neither provide an answer to my issue: https://groups.google.com/d/msg/elasticsearch/OsGJcxuW1vI/qybPOrgE4fMJ https://groups.google.com/d/msg/elasticsearch/2p9jXbCwRC8/mm4BPt5iQfgJ Any ideas on what I'm doing wrong? Is it because elasticsearch is attempting to search based on the node's hostname (elasticsearch-node-01) instead of the IP address? The hostname, elasticsearch-node-01 isn't valid since it's just generated by passing it to docker. Should I use the IP as the hostname if that's what ES is using to add the node to the cluster? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/d52a92e3-0956-48b6-8816-cea5ed31a412%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
