Hey Matt,
I'd like to understand better what is happening here. Could you gist your elasticsearch.yml files (the ones for elasticsearch standard nodes and the tribe node one)? Of course, replace your EC2 credentials by dummy values! :) Thanks! -- David Pilato | Technical Advocate | Elasticsearch.com @dadoonet | @elasticsearchfr Le 7 avril 2014 à 18:03:32, Matt Dainty ([email protected]) a écrit: Hi, I have a ES cluster built in EC2, using the cloud-aws plugin for discovery. The nodes are using their private IP addresses for communication and everything works ok. I want to run one or more tribe nodes remotely, so I point the tribe node to the public IP addresses of some of the nodes however this doesn't work as the network.publish_host setting on each node in the cluster defaults to pointing at its private address. I realised that using the public EC2 DNS names within EC2 points to the private IP addresses of each node still so I reconfigured my cluster to use discovery.ec2.host_type=public_dns and also set network.publish_host=_ec2:publicDns_ . The cluster still works as before with the traffic still using the private IP addresses. However my tribe node still complains it can't reach the private IP address of the nodes; I was expecting it to get the public ec2-X-X-X-X.....amazonaws.com name and resolve it to then gain the public IP address, which should then hopefully work. On two nodes in the cluster if I fetch http://localhost:9200/_nodes/node1,node2/transport?pretty on both node1 and node2 then I notice that the publish_address for the local node is reported as "inet[ec2-X-X-X-X....amazonaws.com/10.0.0.1:9300]" but the publish_address for the non-local node is only reported as being "inet[/10.0.0.2:9300]". Would this mean the the tribe node when connecting remotely still only gets "inet[/10.0.0.x:9300]" for each node address? Am I misunderstanding how this is supposed to work? Is there an alternative way to attach a remote tribe node to this cluster easily? Thanks Matt -- 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/20140407160348.GX2245%40simulant.bodgit-n-scarper.com. For more options, visit https://groups.google.com/d/optout. -- 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/etPan.5343aa37.66ef438d.164d%40MacBook-Air-de-David.local. For more options, visit https://groups.google.com/d/optout.
