Cant create cluster on ec2

Elastic Stack Elasticsearch
1

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+unsubscribe@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.

2

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 (davidmontgomery@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+unsubscribe@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/etPan.52e69b6c.2901d82.b15f%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/groups/opt_out.

3

Hi,

I have the same sec group. Just staying that not having ports open is not
an issue. ES is running on both nodes. Both nodes cant talk. Those fro
ES..anyu suggestions? Do those from ES follow this group?

thanks

On Tue, Jan 28, 2014 at 1:46 AM, David Pilato david@pilato.fr 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 (
davidmontgomery@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+unsubscribe@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/CACF%2B8rqw5_jPrdenE9crYHGZX-7QEtWDKnWhv0M6ch3durjO%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

4

Could you change to TRACE level discovery package?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 18:52, David Montgomery davidmontgomery@gmail.com a écrit :

Hi,

I have the same sec group. Just staying that not having ports open is not an issue. ES is running on both nodes. Both nodes cant talk. Those fro ES..anyu suggestions? Do those from ES follow this group?

thanks

On Tue, Jan 28, 2014 at 1:46 AM, David Pilato david@pilato.fr 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 | @elasticsearchfr

Le 27 janvier 2014 at 18:07:48, David Montgomery (davidmontgomery@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+unsubscribe@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/CACF%2B8rqw5_jPrdenE9crYHGZX-7QEtWDKnWhv0M6ch3durjO%2BQ%40mail.gmail.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/0FAF15FD-9CCC-40F1-B2E5-26C1CB401EEA%40pilato.fr.
For more options, visit https://groups.google.com/groups/opt_out.

5

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

will 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<javascript:>)
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 <javascript:>.
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/ea43ded6-cb4a-45d4-b120-980718476983%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

6

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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

7

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.

8

Yes. Could you gist it (and remove first keys / secrets of course)?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery davidmontgomery@gmail.com a écrit :

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 will 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 | @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/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%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/54FB49BA-850A-4A7F-92E3-EAF51F27A3E6%40pilato.fr.
For more options, visit https://groups.google.com/groups/opt_out.

9

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its not.........again given
that the two machine can talk to each other via telent, in the same region,
same sec group restarted services etc....no go......no cluster

So....how do I manually configure nodes? I have given up on auto
discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["0.test.com:9200", "1.test.com:9200"]

Thanks

On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:

Yes. Could you gist it (and remove first keys / secrets of course)?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery <davidmo...@gmail.com<javascript:>>
a écrit :

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
http://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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

10

Is it a known problem? Not yet. That's the reason I'm asking for logs. I would like to understand what is happening here. So full logs on both nodes would help.

The way you set unicast is fine to me. But please, could you share with me (even through Direct mail) your elasticsearch.yml file and your logs in TRACE level?
You can replace your credentials settings with XXXXXXXX. Please don't change anything else. I'd like to reproduce your case.

Thanks!

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 22:57, David Montgomery davidmontgomery@gmail.com a écrit :

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its not.........again given that the two machine can talk to each other via telent, in the same region, same sec group restarted services etc....no go......no cluster

So....how do I manually configure nodes? I have given up on auto discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["0.test.com:9200", "1.test.com:9200"]

Thanks

On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:
Yes. Could you gist it (and remove first keys / secrets of course)?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery davidmo...@gmail.com a écrit :

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 will 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 | @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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%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/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr.
For more options, visit https://groups.google.com/groups/opt_out.

11

sure..let me the logs together and will post two files ..one log file for
each of the servers.

Thanks

On Tue, Jan 28, 2014 at 6:25 AM, David Pilato david@pilato.fr wrote:

Is it a known problem? Not yet. That's the reason I'm asking for logs. I
would like to understand what is happening here. So full logs on both nodes
would help.

The way you set unicast is fine to me. But please, could you share with me
(even through Direct mail) your elasticsearch.yml file and your logs in
TRACE level?
You can replace your credentials settings with XXXXXXXX. Please don't
change anything else. I'd like to reproduce your case.

Thanks!

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 22:57, David Montgomery davidmontgomery@gmail.com a
écrit :

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its not.........again
given that the two machine can talk to each other via telent, in the same
region, same sec group restarted services etc....no go......no cluster

So....how do I manually configure nodes? I have given up on auto
discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["0.test.com:9200", "1.test.com:9200"]

Thanks

On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:

Yes. Could you gist it (and remove first keys / secrets of course)?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery davidmo...@gmail.com a
écrit :

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
reference/current/modules-discovery-zen.html will 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
http://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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%
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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr
.

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/CACF%2B8rojiupZM9zYongESZzMV8GEn7SNHjTYij%2B9oS%3DA0xz3SA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

12

Hi,

Details

  1. both servers are sing the same sec group
    2 all ports between 9200 and 9300 are open 0.0.0.0/0
  2. ec2 instacances in us-east region
  3. Did a fresh boot on 2 servers both servers are running. Both are not
    talking
  4. Attached are the logs for both servers and the common elasticsearch.yml
    file
  5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with
    elasticsearch-cloud-aws/2.0.0.RC1
    /usr/share/elasticsearch/plugins/cloud-aws
    ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls
    aws-java-sdk-1.3.32.jar commons-codec-1.4.jar commons-logging-1.1.1.jar
    elasticsearch-cloud-aws-2.0.0.RC1.jar httpclient-4.1.1.jar
    httpcore-4.1.jar

data_bag("my_data_bag")
db = data_bag_item("my_data_bag", "my")
AWS_ACCESS_KEY_ID = db[node.chef_environment]['aws']['AWS_ACCESS_KEY_ID']
AWS_SECRET_ACCESS_KEY =
db[node.chef_environment]['aws']['AWS_SECRET_ACCESS_KEY']

version = '1.0.0.RC1'
remote_file
"#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb" do
source "
https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#{version}.deb
"
action :create_if_missing
end

dpkg_package
"#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb" do
action :install
end
bash "add_aws" do
cwd "/usr/share/elasticsearch"
code <<-EOH
git clone GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch
/usr/share/elasticsearch/bin/plugin -install
elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1
EOH
not_if {File.exists?("/usr/share/elasticsearch/elasticsearch-cloud-aws")}
end

service "elasticsearch" do
supports :restart => true, :start => true, :stop => true
action [ :enable, :start]
end

template "/etc/elasticsearch/logging.yml" do
path "/etc/elasticsearch/logging.yml"
source "logging.yml.erb"
owner "root"
group "root"
mode "0755"
notifies :restart, resources(:service => "elasticsearch")
end

template "/etc/elasticsearch/elasticsearch.yml" do
path "/etc/elasticsearch/elasticsearch.yml"
source "elasticsearch.yml.erb"
owner "root"
group "root"
mode "0755"
variables :AWS_ACCESS_KEY_ID => "#{AWS_ACCESS_KEY_ID}",
:AWS_SECRET_ACCESS_KEY => "#{AWS_SECRET_ACCESS_KEY}", :region => "us-east-1"
notifies :restart, resources(:service => "elasticsearch")
end

On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery <davidmontgomery@gmail.com

wrote:

sure..let me the logs together and will post two files ..one log file for
each of the servers.

Thanks

On Tue, Jan 28, 2014 at 6:25 AM, David Pilato david@pilato.fr wrote:

Is it a known problem? Not yet. That's the reason I'm asking for logs. I
would like to understand what is happening here. So full logs on both nodes
would help.

The way you set unicast is fine to me. But please, could you share with
me (even through Direct mail) your elasticsearch.yml file and your logs in
TRACE level?
You can replace your credentials settings with XXXXXXXX. Please don't
change anything else. I'd like to reproduce your case.

Thanks!

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 22:57, David Montgomery davidmontgomery@gmail.com a
écrit :

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its not.........again
given that the two machine can talk to each other via telent, in the same
region, same sec group restarted services etc....no go......no cluster

So....how do I manually configure nodes? I have given up on auto
discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["0.test.com:9200", "1.test.com:9200"]

Thanks

On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:

Yes. Could you gist it (and remove first keys / secrets of course)?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery davidmo...@gmail.com a
écrit :

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
reference/current/modules-discovery-zen.html will 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
http://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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%
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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr
.

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/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

13

Did you override your network.host configuration parameter by any chance?

--
Ivan

On Wed, Jan 29, 2014 at 1:56 PM, David Montgomery <davidmontgomery@gmail.com

wrote:

Hi,

Details

  1. both servers are sing the same sec group
    2 all ports between 9200 and 9300 are open 0.0.0.0/0
  2. ec2 instacances in us-east region
  3. Did a fresh boot on 2 servers both servers are running. Both are not
    talking
  4. Attached are the logs for both servers and the common elasticsearch.yml
    file
  5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with
    elasticsearch-cloud-aws/2.0.0.RC1
    /usr/share/elasticsearch/plugins/cloud-aws
    ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls
    aws-java-sdk-1.3.32.jar commons-codec-1.4.jar commons-logging-1.1.1.jar
    elasticsearch-cloud-aws-2.0.0.RC1.jar httpclient-4.1.1.jar
    httpcore-4.1.jar

data_bag("my_data_bag")
db = data_bag_item("my_data_bag", "my")
AWS_ACCESS_KEY_ID = db[node.chef_environment]['aws']['AWS_ACCESS_KEY_ID']
AWS_SECRET_ACCESS_KEY =
db[node.chef_environment]['aws']['AWS_SECRET_ACCESS_KEY']

version = '1.0.0.RC1'
remote_file
"#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb" do
source "
https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#{version}.deb
"
action :create_if_missing
end

dpkg_package
"#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb" do
action :install
end
bash "add_aws" do
cwd "/usr/share/elasticsearch"
code <<-EOH
git clone GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch
/usr/share/elasticsearch/bin/plugin -install
elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1
EOH
not_if {File.exists?("/usr/share/elasticsearch/elasticsearch-cloud-aws")}
end

service "elasticsearch" do
supports :restart => true, :start => true, :stop => true
action [ :enable, :start]
end

template "/etc/elasticsearch/logging.yml" do
path "/etc/elasticsearch/logging.yml"
source "logging.yml.erb"
owner "root"
group "root"
mode "0755"
notifies :restart, resources(:service => "elasticsearch")
end

template "/etc/elasticsearch/elasticsearch.yml" do
path "/etc/elasticsearch/elasticsearch.yml"
source "elasticsearch.yml.erb"
owner "root"
group "root"
mode "0755"
variables :AWS_ACCESS_KEY_ID => "#{AWS_ACCESS_KEY_ID}",
:AWS_SECRET_ACCESS_KEY => "#{AWS_SECRET_ACCESS_KEY}", :region => "us-east-1"
notifies :restart, resources(:service => "elasticsearch")
end

On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery <
davidmontgomery@gmail.com> wrote:

sure..let me the logs together and will post two files ..one log file for
each of the servers.

Thanks

On Tue, Jan 28, 2014 at 6:25 AM, David Pilato david@pilato.fr wrote:

Is it a known problem? Not yet. That's the reason I'm asking for logs. I
would like to understand what is happening here. So full logs on both nodes
would help.

The way you set unicast is fine to me. But please, could you share with
me (even through Direct mail) your elasticsearch.yml file and your logs in
TRACE level?
You can replace your credentials settings with XXXXXXXX. Please don't
change anything else. I'd like to reproduce your case.

Thanks!

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 22:57, David Montgomery davidmontgomery@gmail.com
a écrit :

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its not.........again
given that the two machine can talk to each other via telent, in the same
region, same sec group restarted services etc....no go......no cluster

So....how do I manually configure nodes? I have given up on auto
discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["0.test.com:9200", "1.test.com:9200"]

Thanks

On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:

Yes. Could you gist it (and remove first keys / secrets of course)?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery davidmo...@gmail.com a
écrit :

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
reference/current/modules-discovery-zen.html will 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
http://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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%
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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr
.

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/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.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/CALY%3DcQDHsDjF0AGUAoC3rLz_y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

14

Hi,

In chef I used -N flag which changes the host name when using chef-client.
I removed the flag and built again. No difference. I have two nodes
running. Both have the name cluster name, ports are 100% wide open...and
wow..ES cant talk despite both running in the same region.

So...ES...any suggestions?

root@ip-10-238-131-236:/var/log/elasticsearch# hostname
ip-10-238-131-236

root@ip-10-238-131-236:/var/log/elasticsearch# curl -XGET '
http://127.0.0.1:9200/_cluster/health?pretty=true'
{
"cluster_name" : "mizilaelasticsearch",
"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
}

On Fri, Jan 31, 2014 at 12:20 AM, Ivan Brusic ivan@brusic.com wrote:

Did you override your network.host configuration parameter by any chance?

--
Ivan

On Wed, Jan 29, 2014 at 1:56 PM, David Montgomery <
davidmontgomery@gmail.com> wrote:

Hi,

Details

  1. both servers are sing the same sec group
    2 all ports between 9200 and 9300 are open 0.0.0.0/0
  2. ec2 instacances in us-east region
  3. Did a fresh boot on 2 servers both servers are running. Both are not
    talking
  4. Attached are the logs for both servers and the common
    elasticsearch.yml file
  5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with
    elasticsearch-cloud-aws/2.0.0.RC1
    /usr/share/elasticsearch/plugins/cloud-aws
    ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls
    aws-java-sdk-1.3.32.jar commons-codec-1.4.jar
    commons-logging-1.1.1.jar elasticsearch-cloud-aws-2.0.0.RC1.jar
    httpclient-4.1.1.jar httpcore-4.1.jar

data_bag("my_data_bag")
db = data_bag_item("my_data_bag", "my")
AWS_ACCESS_KEY_ID = db[node.chef_environment]['aws']['AWS_ACCESS_KEY_ID']
AWS_SECRET_ACCESS_KEY =
db[node.chef_environment]['aws']['AWS_SECRET_ACCESS_KEY']

version = '1.0.0.RC1'
remote_file
"#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb" do
source "
https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#{version}.deb
"
action :create_if_missing
end

dpkg_package
"#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb" do
action :install
end
bash "add_aws" do
cwd "/usr/share/elasticsearch"
code <<-EOH
git clone
GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch
/usr/share/elasticsearch/bin/plugin -install
elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1
EOH
not_if
{File.exists?("/usr/share/elasticsearch/elasticsearch-cloud-aws")}
end

service "elasticsearch" do
supports :restart => true, :start => true, :stop => true
action [ :enable, :start]
end

template "/etc/elasticsearch/logging.yml" do
path "/etc/elasticsearch/logging.yml"
source "logging.yml.erb"
owner "root"
group "root"
mode "0755"
notifies :restart, resources(:service => "elasticsearch")
end

template "/etc/elasticsearch/elasticsearch.yml" do
path "/etc/elasticsearch/elasticsearch.yml"
source "elasticsearch.yml.erb"
owner "root"
group "root"
mode "0755"
variables :AWS_ACCESS_KEY_ID => "#{AWS_ACCESS_KEY_ID}",
:AWS_SECRET_ACCESS_KEY => "#{AWS_SECRET_ACCESS_KEY}", :region => "us-east-1"
notifies :restart, resources(:service => "elasticsearch")
end

On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery <
davidmontgomery@gmail.com> wrote:

sure..let me the logs together and will post two files ..one log file
for each of the servers.

Thanks

On Tue, Jan 28, 2014 at 6:25 AM, David Pilato david@pilato.fr wrote:

Is it a known problem? Not yet. That's the reason I'm asking for logs.
I would like to understand what is happening here. So full logs on both
nodes would help.

The way you set unicast is fine to me. But please, could you share with
me (even through Direct mail) your elasticsearch.yml file and your logs in
TRACE level?
You can replace your credentials settings with XXXXXXXX. Please don't
change anything else. I'd like to reproduce your case.

Thanks!

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 22:57, David Montgomery davidmontgomery@gmail.com
a écrit :

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its not.........again
given that the two machine can talk to each other via telent, in the same
region, same sec group restarted services etc....no go......no cluster

So....how do I manually configure nodes? I have given up on auto
discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["0.test.com:9200", "1.test.com
:9200"]

Thanks

On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:

Yes. Could you gist it (and remove first keys / secrets of course)?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery davidmo...@gmail.com a
écrit :

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
reference/current/modules-discovery-zen.html will 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
http://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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%
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/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr
.

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/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDHsDjF0AGUAoC3rLz_y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.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/CACF%2B8rrWR0AgKk%2B%3DZkR-g3b9EEW_H-V4m-THh%2B50ct-gfqEb_g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

15

Hello David and David,

I took a look at the logs / configs posted and mine are mostly similar
(though i'm not using any rivers) and I'm having the same issue.
I've tested on 0.90.9 and 0.90.7, I hadn't tried the 1.0.0RC yet because
the logstash website suggested I stick to 0.90.9
If you need any more logs / config samples I'd be happy to provide those.

Best,
JG

On Friday, January 31, 2014 3:46:07 PM UTC-5, David Montgomery wrote:

Hi,

In chef I used -N flag which changes the host name when using
chef-client. I removed the flag and built again. No difference. I have
two nodes running. Both have the name cluster name, ports are 100% wide
open...and wow..ES cant talk despite both running in the same region.

So...ES...any suggestions?

root@ip-10-238-131-236:/var/log/elasticsearch# hostname
ip-10-238-131-236

root@ip-10-238-131-236:/var/log/elasticsearch# curl -XGET '
http://127.0.0.1:9200/_cluster/health?pretty=true'
{
"cluster_name" : "mizilaelasticsearch",
"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
}

On Fri, Jan 31, 2014 at 12:20 AM, Ivan Brusic <iv...@brusic.com<javascript:>

wrote:

Did you override your network.host configuration parameter by any chance?

--
Ivan

On Wed, Jan 29, 2014 at 1:56 PM, David Montgomery <davidmo...@gmail.com<javascript:>

wrote:

Hi,

Details

  1. both servers are sing the same sec group
    2 all ports between 9200 and 9300 are open 0.0.0.0/0
  2. ec2 instacances in us-east region
  3. Did a fresh boot on 2 servers both servers are running. Both are not
    talking
  4. Attached are the logs for both servers and the common
    elasticsearch.yml file
  5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with
    elasticsearch-cloud-aws/2.0.0.RC1
    /usr/share/elasticsearch/plugins/cloud-aws
    ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls
    aws-java-sdk-1.3.32.jar commons-codec-1.4.jar
    commons-logging-1.1.1.jar elasticsearch-cloud-aws-2.0.0.RC1.jar
    httpclient-4.1.1.jar httpcore-4.1.jar

data_bag("my_data_bag")
db = data_bag_item("my_data_bag", "my")
AWS_ACCESS_KEY_ID = db[node.chef_environment]['aws']['AWS_ACCESS_KEY_ID']
AWS_SECRET_ACCESS_KEY =
db[node.chef_environment]['aws']['AWS_SECRET_ACCESS_KEY']

version = '1.0.0.RC1'
remote_file
"#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb" do
source "
https://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-#{version}.deb
"
action :create_if_missing
end

dpkg_package
"#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb" do
action :install
end
bash "add_aws" do
cwd "/usr/share/elasticsearch"
code <<-EOH
git clone
GitHub - elastic/elasticsearch-cloud-aws: AWS Cloud Plugin for Elasticsearch
/usr/share/elasticsearch/bin/plugin -install
elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1
EOH
not_if
{File.exists?("/usr/share/elasticsearch/elasticsearch-cloud-aws")}
end

service "elasticsearch" do
supports :restart => true, :start => true, :stop => true
action [ :enable, :start]
end

template "/etc/elasticsearch/logging.yml" do
path "/etc/elasticsearch/logging.yml"
source "logging.yml.erb"
owner "root"
group "root"
mode "0755"
notifies :restart, resources(:service => "elasticsearch")
end

template "/etc/elasticsearch/elasticsearch.yml" do
path "/etc/elasticsearch/elasticsearch.yml"
source "elasticsearch.yml.erb"
owner "root"
group "root"
mode "0755"
variables :AWS_ACCESS_KEY_ID => "#{AWS_ACCESS_KEY_ID}",
:AWS_SECRET_ACCESS_KEY => "#{AWS_SECRET_ACCESS_KEY}", :region => "us-east-1"
notifies :restart, resources(:service => "elasticsearch")
end

On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery <davidmo...@gmail.com<javascript:>

wrote:

sure..let me the logs together and will post two files ..one log file
for each of the servers.

Thanks

On Tue, Jan 28, 2014 at 6:25 AM, David Pilato <da...@pilato.fr<javascript:>

wrote:

Is it a known problem? Not yet. That's the reason I'm asking for logs.
I would like to understand what is happening here. So full logs on both
nodes would help.

The way you set unicast is fine to me. But please, could you share
with me (even through Direct mail) your elasticsearch.yml file and your
logs in TRACE level?
You can replace your credentials settings with XXXXXXXX. Please don't
change anything else. I'd like to reproduce your case.

Thanks!

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 22:57, David Montgomery <davidmo...@gmail.com<javascript:>>
a écrit :

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its not.........again
given that the two machine can talk to each other via telent, in the same
region, same sec group restarted services etc....no go......no cluster

So....how do I manually configure nodes? I have given up on auto
discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["0.test.com:9200", "1.test.com
:9200"]

Thanks

On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:

Yes. Could you gist it (and remove first keys / secrets of course)?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery davidmo...@gmail.com a
écrit :

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
reference/current/modules-discovery-zen.html will 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
http://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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/4d1c068a-3e9c-4731-84e2-62eeeb63fa81%
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 elasticsearc...@googlegroups.com <javascript:>.

To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%40googlegroups.com
.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr
.

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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQDHsDjF0AGUAoC3rLz_y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.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/a48fe555-0b95-4281-ba9e-351b21f4a9e9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

16

Hi Jonathan

Just be clear...you could not cluster? I wili try the lastest stable
release cuase I am giving up on 1.0.0RC.

Thanks

On Sun, Feb 2, 2014 at 10:10 AM, Jonathan Goodwin <
jonathanwgoodwin@gmail.com> wrote:

Hello David and David,

I took a look at the logs / configs posted and mine are mostly similar
(though i'm not using any rivers) and I'm having the same issue.
I've tested on 0.90.9 and 0.90.7, I hadn't tried the 1.0.0RC yet because
the logstash website suggested I stick to 0.90.9
If you need any more logs / config samples I'd be happy to provide those.

Best,
JG

On Friday, January 31, 2014 3:46:07 PM UTC-5, David Montgomery wrote:

Hi,

In chef I used -N flag which changes the host name when using
chef-client. I removed the flag and built again. No difference. I have
two nodes running. Both have the name cluster name, ports are 100% wide
open...and wow..ES cant talk despite both running in the same region.

So...ES...any suggestions?

root@ip-10-238-131-236:/var/log/elasticsearch# hostname
ip-10-238-131-236

root@ip-10-238-131-236:/var/log/elasticsearch# curl -XGET '
http://127.0.0.1:9200/_cluster/health?pretty=true'
{
"cluster_name" : "mizilaelasticsearch",
"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
}

On Fri, Jan 31, 2014 at 12:20 AM, Ivan Brusic iv...@brusic.com wrote:

Did you override your network.host configuration parameter by any chance?

--
Ivan

On Wed, Jan 29, 2014 at 1:56 PM, David Montgomery davidmo...@gmail.comwrote:

Hi,

Details

  1. both servers are sing the same sec group
    2 all ports between 9200 and 9300 are open 0.0.0.0/0
  2. ec2 instacances in us-east region
  3. Did a fresh boot on 2 servers both servers are running. Both are
    not talking
  4. Attached are the logs for both servers and the common
    elasticsearch.yml file
  5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with
    elasticsearch-cloud-aws/2.0.0.RC1
    /usr/share/elasticsearch/plugins/cloud-aws
    ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls
    aws-java-sdk-1.3.32.jar commons-codec-1.4.jar
    commons-logging-1.1.1.jar elasticsearch-cloud-aws-2.0.0.RC1.jar
    httpclient-4.1.1.jar httpcore-4.1.jar

data_bag("my_data_bag")
db = data_bag_item("my_data_bag", "my")
AWS_ACCESS_KEY_ID = db[node.chef_environment]['
aws']['AWS_ACCESS_KEY_ID']
AWS_SECRET_ACCESS_KEY = db[node.chef_environment]['
aws']['AWS_SECRET_ACCESS_KEY']

version = '1.0.0.RC1'
remote_file "#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb"
do
source "https://download.elasticsearch.org/
elasticsearch/elasticsearch/elasticsearch-#{version}.deb"
action :create_if_missing
end

dpkg_package "#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb"
do
action :install
end
bash "add_aws" do
cwd "/usr/share/elasticsearch"
code <<-EOH
git clone https://github.com/elasticsearch/elasticsearch-
cloud-aws.git
/usr/share/elasticsearch/bin/plugin -install
elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1
EOH
not_if {File.exists?("/usr/share/elasticsearch/elasticsearch-
cloud-aws")}
end

service "elasticsearch" do
supports :restart => true, :start => true, :stop => true
action [ :enable, :start]
end

template "/etc/elasticsearch/logging.yml" do
path "/etc/elasticsearch/logging.yml"
source "logging.yml.erb"
owner "root"
group "root"
mode "0755"
notifies :restart, resources(:service => "elasticsearch")
end

template "/etc/elasticsearch/elasticsearch.yml" do
path "/etc/elasticsearch/elasticsearch.yml"
source "elasticsearch.yml.erb"
owner "root"
group "root"
mode "0755"
variables :AWS_ACCESS_KEY_ID => "#{AWS_ACCESS_KEY_ID}",
:AWS_SECRET_ACCESS_KEY => "#{AWS_SECRET_ACCESS_KEY}", :region => "us-east-1"
notifies :restart, resources(:service => "elasticsearch")
end

On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery <davidmo...@gmail.com

wrote:

sure..let me the logs together and will post two files ..one log file
for each of the servers.

Thanks

On Tue, Jan 28, 2014 at 6:25 AM, David Pilato da...@pilato.fr wrote:

Is it a known problem? Not yet. That's the reason I'm asking for
logs. I would like to understand what is happening here. So full logs on
both nodes would help.

The way you set unicast is fine to me. But please, could you share
with me (even through Direct mail) your elasticsearch.yml file and your
logs in TRACE level?
You can replace your credentials settings with XXXXXXXX. Please don't
change anything else. I'd like to reproduce your case.

Thanks!

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 22:57, David Montgomery davidmo...@gmail.com a
écrit :

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its not.........again
given that the two machine can talk to each other via telent, in the same
region, same sec group restarted services etc....no go......no cluster

So....how do I manually configure nodes? I have given up on auto
discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["0.test.com:9200", "1.test.com
:9200"]

Thanks

On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:

Yes. Could you gist it (and remove first keys / secrets of course)?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery davidmo...@gmail.com a
écrit :

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
e/current/modules-discovery-zen.html will 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
http://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-c6b
2-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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/4d1c068a-3e9
c-4731-84e2-62eeeb63fa81%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 elasticsearc...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/2bdefbe0-3ab4-4b85-b473-8b502b812d5b%
40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in
the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/2804A7F6-B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr.

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%
2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/CALY%3DcQDHsDjF0AGUAoC3rLz_
y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a48fe555-0b95-4281-ba9e-351b21f4a9e9%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/CACF%2B8rqhd%2BRx7Ku41iGukxYFD%2B-xoPvMyFW-%2Bw%3DLdQuzDTctJA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

17

Just tried 0.90.11. Same issue. I have two running nodes on ec2..and
wow...they cant talk.

On Tue, Feb 4, 2014 at 6:51 AM, David Montgomery
davidmontgomery@gmail.comwrote:

Hi Jonathan

Just be clear...you could not cluster? I wili try the lastest stable
release cuase I am giving up on 1.0.0RC.

Thanks

On Sun, Feb 2, 2014 at 10:10 AM, Jonathan Goodwin <
jonathanwgoodwin@gmail.com> wrote:

Hello David and David,

I took a look at the logs / configs posted and mine are mostly similar
(though i'm not using any rivers) and I'm having the same issue.
I've tested on 0.90.9 and 0.90.7, I hadn't tried the 1.0.0RC yet because
the logstash website suggested I stick to 0.90.9
If you need any more logs / config samples I'd be happy to provide those.

Best,
JG

On Friday, January 31, 2014 3:46:07 PM UTC-5, David Montgomery wrote:

Hi,

In chef I used -N flag which changes the host name when using
chef-client. I removed the flag and built again. No difference. I have
two nodes running. Both have the name cluster name, ports are 100% wide
open...and wow..ES cant talk despite both running in the same region.

So...ES...any suggestions?

root@ip-10-238-131-236:/var/log/elasticsearch# hostname
ip-10-238-131-236

root@ip-10-238-131-236:/var/log/elasticsearch# curl -XGET '
http://127.0.0.1:9200/_cluster/health?pretty=true'
{
"cluster_name" : "mizilaelasticsearch",
"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
}

On Fri, Jan 31, 2014 at 12:20 AM, Ivan Brusic iv...@brusic.com wrote:

Did you override your network.host configuration parameter by any
chance?

--
Ivan

On Wed, Jan 29, 2014 at 1:56 PM, David Montgomery <davidmo...@gmail.com

wrote:

Hi,

Details

  1. both servers are sing the same sec group
    2 all ports between 9200 and 9300 are open 0.0.0.0/0
  2. ec2 instacances in us-east region
  3. Did a fresh boot on 2 servers both servers are running. Both are
    not talking
  4. Attached are the logs for both servers and the common
    elasticsearch.yml file
  5. Below is he chef recipe I wrote. I am using 1.0.0.RC1 with
    elasticsearch-cloud-aws/2.0.0.RC1
    /usr/share/elasticsearch/plugins/cloud-aws
    ubuntu@ip-10-73-142-187:/usr/share/elasticsearch/plugins/cloud-aws$ ls
    aws-java-sdk-1.3.32.jar commons-codec-1.4.jar
    commons-logging-1.1.1.jar elasticsearch-cloud-aws-2.0.0.RC1.jar
    httpclient-4.1.1.jar httpcore-4.1.jar

data_bag("my_data_bag")
db = data_bag_item("my_data_bag", "my")
AWS_ACCESS_KEY_ID = db[node.chef_environment]['
aws']['AWS_ACCESS_KEY_ID']
AWS_SECRET_ACCESS_KEY = db[node.chef_environment]['
aws']['AWS_SECRET_ACCESS_KEY']

version = '1.0.0.RC1'
remote_file "#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb"
do
source "https://download.elasticsearch.org/
elasticsearch/elasticsearch/elasticsearch-#{version}.deb"
action :create_if_missing
end

dpkg_package "#{Chef::Config[:file_cache_path]}/elasticsearch-#{version}.deb"
do
action :install
end
bash "add_aws" do
cwd "/usr/share/elasticsearch"
code <<-EOH
git clone https://github.com/elasticsearch/elasticsearch-
cloud-aws.git
/usr/share/elasticsearch/bin/plugin -install
elasticsearch/elasticsearch-cloud-aws/2.0.0.RC1
EOH
not_if {File.exists?("/usr/share/elasticsearch/elasticsearch-
cloud-aws")}
end

service "elasticsearch" do
supports :restart => true, :start => true, :stop => true
action [ :enable, :start]
end

template "/etc/elasticsearch/logging.yml" do
path "/etc/elasticsearch/logging.yml"
source "logging.yml.erb"
owner "root"
group "root"
mode "0755"
notifies :restart, resources(:service => "elasticsearch")
end

template "/etc/elasticsearch/elasticsearch.yml" do
path "/etc/elasticsearch/elasticsearch.yml"
source "elasticsearch.yml.erb"
owner "root"
group "root"
mode "0755"
variables :AWS_ACCESS_KEY_ID => "#{AWS_ACCESS_KEY_ID}",
:AWS_SECRET_ACCESS_KEY => "#{AWS_SECRET_ACCESS_KEY}", :region => "us-east-1"
notifies :restart, resources(:service => "elasticsearch")
end

On Tue, Jan 28, 2014 at 6:40 AM, David Montgomery <
davidmo...@gmail.com> wrote:

sure..let me the logs together and will post two files ..one log file
for each of the servers.

Thanks

On Tue, Jan 28, 2014 at 6:25 AM, David Pilato da...@pilato.frwrote:

Is it a known problem? Not yet. That's the reason I'm asking for
logs. I would like to understand what is happening here. So full logs on
both nodes would help.

The way you set unicast is fine to me. But please, could you share
with me (even through Direct mail) your elasticsearch.yml file and your
logs in TRACE level?
You can replace your credentials settings with XXXXXXXX. Please
don't change anything else. I'd like to reproduce your case.

Thanks!

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 22:57, David Montgomery davidmo...@gmail.com a
écrit :

I have to say..it this a know problem?

I removed the keys.

So.. should the servers still cluster? Well....its
not.........again given that the two machine can talk to each other via
telent, in the same region, same sec group restarted services etc....no
go......no cluster

So....how do I manually configure nodes? I have given up on auto
discover. Clearly does now work for me.

Is the below an example?

discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["0.test.com:9200", "1.test.com
:9200"]

Thanks

On Tuesday, January 28, 2014 4:19:25 AM UTC+8, David Pilato wrote:

Yes. Could you gist it (and remove first keys / secrets of course)?

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 27 janv. 2014 à 20:53, David Montgomery davidmo...@gmail.com
a écrit :

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
e/current/modules-discovery-zen.html will 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
http://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-c6b
2-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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/4d1c068a-3e9
c-4731-84e2-62eeeb63fa81%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 elasticsearc...@googlegroups.com.

To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2bdefbe0-
3ab4-4b85-b473-8b502b812d5b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in
the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/2804A7F6-
B2B8-4C23-B273-B7B7E0F805E0%40pilato.fr.

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/CACF%2B8roDUwpq--dH9eAUoo-Xe-GEtgH%
2B7WDJrbgjPWJBV2ijFQ%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/CALY%3DcQDHsDjF0AGUAoC3rLz_
y5eGvFPtDEooRj0xP87mRjxurg%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/PDDOu42M9Mc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a48fe555-0b95-4281-ba9e-351b21f4a9e9%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/CACF%2B8ro6cwQ1pw6nbMo3ciX85q7Gen5s%2BS%2B1THuebiM130dihQ%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.