If this is what you mean my trace in the logs....
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
[2014-01-27 16:58:49,706][TRACE][discovery.zen.ping.unicast]
[Administrator] [1] failed to connect to
[#cloud-i-ef763797-0][aws-elasticsearch-east-development-20140127160434][inet[/10.198.91.74:9300]]
org.elasticsearch.transport.ConnectTransportException:
[inet[/10.198.91.74: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
[2014-01-27 16:58:49,707][TRACE][discovery.zen.ping.unicast]
[Administrator] [1] failed to connect to
[#cloud-i-0598a260-0][aws-elasticsearch-east-development-20140127160434][inet[/10.244.178.236:9300]]
org.elasticsearch.transport.ConnectTransportException:
[inet[/10.244.178.236: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
[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
[2014-01-27 17:38:09,856][DEBUG][discovery.zen.ping.unicast] [Lupa] using
initial hosts , with concurrent_connects [10]
[2014-01-27 17:38:09,949][DEBUG][discovery.ec2 ] [Lupa] using
ping.timeout [3s], master_election.filter_client [true],
master_election.filter_data [false]
[2014-01-27 17:38:09,950][DEBUG][discovery.zen.elect ] [Lupa] using
minimum_master_nodes [-1]
[2014-01-27 17:38:09,951][DEBUG][discovery.zen.fd ] [Lupa] [master]
uses ping_interval [1s], ping_timeout [30s], ping_retries [3]
[2014-01-27 17:38:09,963][DEBUG][discovery.zen.fd ] [Lupa] [node ]
uses ping_interval [1s], ping_timeout [30s], ping_retries [3]
[2014-01-27 17:38:11,361][DEBUG][discovery.ec2 ] [Lupa] using
host_type [PRIVATE_IP], tags [{}], groups [] with any_group [true],
availability_zones []
[2014-01-27 17:38:14,205][WARN ][gateway.s3 ] [Lupa] shared
gateway has been deprecated, please use the (default) local gateway
[2014-01-27 17:38:14,207][WARN ][gateway.s3 ] [Lupa] shared
gateway has been deprecated, please use the (default) local gateway
[2014-01-27 17:39:48,081][INFO ][node ] [Hurricane]
version[1.0.0.RC1], pid[21245], build[c6155c5/2014-01-15T17:02:32Z]
[2014-01-27 17:39:48,081][INFO ][node ] [Hurricane]
initializing ...
[2014-01-27 17:39:48,107][INFO ][plugins ] [Hurricane]
loaded [cloud-aws], sites
[2014-01-27 17:39:52,291][DEBUG][discovery.zen.ping.multicast] [Hurricane]
using group [224.2.2.4], with port [54328], ttl [3], and address [null]
[2014-01-27 17:39:52,295][DEBUG][discovery.zen.ping.unicast] [Hurricane]
using initial hosts , with concurrent_connects [10]
[2014-01-27 17:39:52,296][DEBUG][discovery.zen ] [Hurricane]
using ping.timeout [3s], master_election.filter_client [true],
master_election.filter_data [false]
[2014-01-27 17:39:52,297][DEBUG][discovery.zen.elect ] [Hurricane]
using minimum_master_nodes [-1]
[2014-01-27 17:39:52,298][DEBUG][discovery.zen.fd ] [Hurricane]
[master] uses ping_interval [1s], ping_timeout [30s], ping_retries [3]
[2014-01-27 17:39:52,307][DEBUG][discovery.zen.fd ] [Hurricane]
[node ] uses ping_interval [1s], ping_timeout [30s], ping_retries [3]
[2014-01-27 17:39:54,818][INFO ][node ] [Hurricane]
initialized
[2014-01-27 17:39:54,819][INFO ][node ] [Hurricane]
starting ...
[2014-01-27 17:39:55,248][INFO ][transport ] [Hurricane]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address
{inet[/10.208.51.152:9300]}
[2014-01-27 17:39:55,259][TRACE][discovery ] [Hurricane]
waiting for 30s for the initial state to be set by the discovery
[2014-01-27 17:39:55,270][TRACE][discovery.zen.ping.multicast] [Hurricane]
[1] sending ping request
[2014-01-27 17:39:56,771][TRACE][discovery.zen.ping.multicast] [Hurricane]
[1] sending ping request
[2014-01-27 17:39:58,273][TRACE][discovery.zen ] [Hurricane]
full ping responses: {none}
[2014-01-27 17:39:58,273][DEBUG][discovery.zen ] [Hurricane]
filtered ping responses: (filter_client[true], filter_data[false]) {none}
[2014-01-27 17:39:58,278][INFO ][cluster.service ] [Hurricane]
new_master
[Hurricane][hFUsfnukS_GLOxCZwJsVXA][aws-elasticsearch-east-development-20140127160434][inet[/10.208.51.152:9300]],
reason: zen-d$
[2014-01-27 17:39:58,308][TRACE][discovery ] [Hurricane]
initial state set from discovery
[2014-01-27 17:39:58,308][INFO ][discovery ] [Hurricane]
mizilaelasticsearch/hFUsfnukS_GLOxCZwJsVXA
[2014-01-27 17:39:58,424][INFO ][http ] [Hurricane]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address
{inet[/10.208.51.152:9200]}
[2014-01-27 17:39:58,444][INFO ][gateway ] [Hurricane]
recovered [0] indices into cluster_state
[2014-01-27 17:39:58,444][INFO ][node ] [Hurricane]
started
[2014-01-27 19:54:52,667][INFO ][node ] [Hurricane]
stopping ...
[2014-01-27 19:54:52,774][INFO ][node ] [Hurricane]
stopped
[2014-01-27 19:54:52,774][INFO ][node ] [Hurricane]
closing ...
[2014-01-27 19:54:52,781][INFO ][node ] [Hurricane]
closed
[2014-01-27 19:54:56,193][INFO ][node ] [Cerise]
version[1.0.0.RC1], pid[21694], build[c6155c5/2014-01-15T17:02:32Z]
[2014-01-27 19:54:56,193][INFO ][node ] [Cerise]
initializing ...
[2014-01-27 19:54:56,208][INFO ][plugins ] [Cerise] loaded
[cloud-aws], sites
[2014-01-27 19:55:01,703][DEBUG][discovery.zen.ping.multicast] [Cerise]
using group [224.2.2.4], with port [54328], ttl [3], and address [null]
[2014-01-27 19:55:01,738][DEBUG][discovery.zen.ping.unicast] [Cerise] using
initial hosts , with concurrent_connects [10]
[2014-01-27 19:55:01,739][DEBUG][discovery.zen ] [Cerise] using
ping.timeout [3s], master_election.filter_client [true],
master_election.filter_data [false]
[2014-01-27 19:55:01,740][DEBUG][discovery.zen.elect ] [Cerise] using
minimum_master_nodes [-1]
[2014-01-27 19:55:01,741][DEBUG][discovery.zen.fd ] [Cerise]
[master] uses ping_interval [1s], ping_timeout [30s], ping_retries [3]
[2014-01-27 19:55:01,752][DEBUG][discovery.zen.fd ] [Cerise] [node
] uses ping_interval [1s], ping_timeout [30s], ping_retries [3]
[2014-01-27 19:55:04,736][INFO ][node ] [Cerise]
initialized
[2014-01-27 19:55:04,736][INFO ][node ] [Cerise]
starting ...
[2014-01-27 19:55:04,981][INFO ][transport ] [Cerise]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address
{inet[/10.208.51.152:9300]}
[2014-01-27 19:55:05,003][TRACE][discovery ] [Cerise]
waiting for 30s for the initial state to be set by the discovery
[2014-01-27 19:55:05,105][TRACE][discovery.zen.ping.multicast] [Cerise] [1]
sending ping request
[2014-01-27 19:55:06,608][TRACE][discovery.zen.ping.multicast] [Cerise] [1]
sending ping request
[2014-01-27 19:55:08,256][TRACE][discovery.zen ] [Cerise] full
ping responses: {none}
[2014-01-27 19:55:08,257][DEBUG][discovery.zen ] [Cerise]
filtered ping responses: (filter_client[true], filter_data[false]) {none}
[2014-01-27 19:55:08,262][INFO ][cluster.service ] [Cerise]
new_master
[Cerise][TOid02a4RMqcyHzEpJEuPg][aws-elasticsearch-east-development-20140127160434][inet[/10.208.51.152:9300]],
reason: zen-disco-j$
[2014-01-27 19:55:08,297][TRACE][discovery ] [Cerise]
initial state set from discovery
On Tuesday, January 28, 2014 3:53:50 AM UTC+8, David Montgomery wrote:
I assume that means this in the logging.yml fike?
discovery
discovery: TRACE
I do have it on...what should I be looking for in the logs?
On Tuesday, January 28, 2014 3:47:10 AM UTC+8, David Montgomery wrote:
Hi,
As an fyi..I can telnet into the other machine. Its only ES that does
not work despite following the online docs.
If ES aws auto discovery does not work l assuming assume that
Elasticsearch Platform — Find real-time answers at scale | Elastic work?
Thanks
On Tuesday, January 28, 2014 1:46:20 AM UTC+8, David Pilato wrote:
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 https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr
Le 27 janvier 2014 at 18:07:48, David Montgomery (davidmo...@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 elasticsearc...@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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1d2ec8d6-ac20-4961-961e-181c2562cd60%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.