The three nodes are connected by an Azure virtual network. They are all part of a single cloud service, operating in a load balanced set. I am not currently using any kind of FQDN, so the unicast host names are "es-machine-1", "es-machine-2" etc. No domain suffix whatsoever. As far as I know that is end-arounding the public load balancer (since none of those hostnames are publicly accessible to machines outside the virtual network). But I've been wrong before :) I actually can't find any kind of fully qualified domain name for those machines, other than the public facing cloudapp.net one, so I assume this is OK? I've also tried using the internal virtual network IP addresses on a similarly specced development cluster, and I see the same timeouts there.
On Friday, May 30, 2014 1:40:47 AM UTC-5, Michael Delaney wrote: > > Are u using internal fully qualified domain names, e.g > es01.myelasticsearcservice.f3.internal.net > If you use public load balancer end points you'll get timeouts. -- 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/dd26798c-66ef-4881-88ea-72d9df2e16a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
