Hi David,
I think you should have nodes running under the same security group. In that case, you don't have to open 9300-9400 ports to public. If they don't belong to the same group or if you want to reach them from outside ec2 platform (public IP), then you need to set host_type to public_ip. It sounds like your nodes are trying to connect with private ip here (which is default). My 2 cents -- David Pilato | Technical Advocate | Elasticsearch.com @dadoonet | @elasticsearchfr Le 27 janvier 2014 at 18:07:48, David Montgomery (davidmontgom...@gmail.com) a écrit: Hi, I have two nodes runnging on ec2. curl -X GET http://localhost:9200/_cluster/health?pretty=true { "cluster_name" : "12345elasticsearch", "status" : "green", "timed_out" : false, "number_of_nodes" : 1, "number_of_data_nodes" : 1, "active_primary_shards" : 0, "active_shards" : 0, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 0 } So..its fair to say that ec2 clustering did not work given the below config. Yes...the aws keys are correct and I have port 9200-9400 open. What elasticsearch advertiseres is that all that is needed. I am using 1.0.0.RC1 with elasticsearch-cloud-aws= 2.0.0.RC1 on ubuntu 12.04 cloud.aws.access_key: <%=@AWS_ACCESS_KEY_ID%> cloud.aws.secret_key: <%=@AWS_SECRET_ACCESS_KEY%> discovery.type: ec2 In the logs I see the below: [2014-01-27 16:58:49,708][TRACE][discovery.zen.ping.unicast] [Administrator] [1] failed to connect to [#cloud-i-1079ac6b-0][aws-elasticsearch-east-development-20140127160434][inet[/10.211.29.210:9300]] org.elasticsearch.transport.ConnectTransportException: [][inet[/10.211.29.210:9300]] connect_timeout[30s] at org.elasticsearch.transport.netty.NettyTransport.connectToChannelsLight(NettyTransport.java:676) at org.elasticsearch.transport.netty.NettyTransport.connectToNode(NettyTransport.java:636) at org.elasticsearch.transport.netty.NettyTransport.connectToNodeLight(NettyTransport.java:603) at org.elasticsearch.transport.TransportService.connectToNodeLight(TransportService.java:133) at org.elasticsearch.discovery.zen.ping.unicast.UnicastZenPing$3.run(UnicastZenPing.java:278) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) Caused by: org.elasticsearch.common.netty.channel.ConnectTimeoutException: connection timed out: /10.239.36.98:9300 at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.processConnectTimeout(NioClientBoss.java:137) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:83) at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) at org.elasticsearch.common.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) ... 3 more Thanks -- 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/ec028f53-c6b2-48e1-b714-a6f1ac7ae1cd%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/etPan.52e69b6c.2901d82.b15f%40MacBook-Air-de-David.local. For more options, visit https://groups.google.com/groups/opt_out.
