Hi, using the transport client solved my issue. It seems the server lookup does not work.
Cheers, Klaus On Tuesday, January 20, 2015 at 12:54:11 PM UTC+1, Itamar Syn-Hershko wrote: > > This requires port 9300 to be open on the cloud for you (UDP), and for > your client code to set the cluster name correctly > > -- > > Itamar Syn-Hershko > http://code972.com | @synhershko <https://twitter.com/synhershko> > Freelance Developer & Consultant > Lucene.NET committer and PMC member > > On Tue, Jan 20, 2015 at 1:52 PM, Klausen Schaefersinho < > klaus.s...@gmail.com <javascript:>> wrote: > >> Hi, >> >> >> I have just the "click to deploy" features to set up a small >> ElasticSearch cluster. That seems to have worked fine and I can connect to >> the cluster of rest. For instance "curl http://<ip>:9200" will return >> >> >> { >> "status" : 200, >> "name" : "elasticsearch-8tqw", >> "cluster_name" : "my_elasticsearch-cluster", >> "version" : {...}, >> "tagline" : "You Know, for Search" >> } >> >> >> So I assume the cluster name is "my_elasticsearch-cluster". However if I >> try to connect to the cluster using the java node client the client takes >> really long to join the cluster and if I try to perform a healt check, just >> to check if I am really connected I get the following exception: >> >> org.elasticsearch.discovery.MasterNotDiscoveredException: waited for [30s] >> at >> org.elasticsearch.action.support.master.TransportMasterNodeOperationAction$4.onTimeout(TransportMasterNodeOperationAction.java:164) >> >> at >> org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:239) >> >> at >> org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:497) >> >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >> >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> >> at java.lang.Thread.run(Thread.java:745) >> >> >> Why does this happen, and how can I solve it? Is there something not >> correctly configured in my network or should I use the transport client? >> >> >> Thanks! >> >> Klaus >> >> -- >> 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 elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/bdc6e797-1656-4dfc-adda-794519a82eaf%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/bdc6e797-1656-4dfc-adda-794519a82eaf%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> 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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e5f58eae-817b-45b3-8825-9a7ae4e76379%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
