ec2 discovery

Elastic Stack Elasticsearch
1

Hi,
I've configured aws ec2 instance as specified in the guide.
But when I'm running bin/elasticsearch -f the output doesn't shows me that
ec2 discovery is actually working and output is next :

[2012-01-15 21:39:52,974][INFO ][node ] [Braddock,
Elizabeth "Betsy"] {0.18.7}[9458]: initializing ...
[2012-01-15 21:39:52,991][INFO ][plugins ] [Braddock,
Elizabeth "Betsy"] loaded [cloud-aws], sites []
[2012-01-15 21:39:58,725][INFO ][node ] [Braddock,
Elizabeth "Betsy"] {0.18.7}[9458]: initialized
[2012-01-15 21:39:58,726][INFO ][node ] [Braddock,
Elizabeth "Betsy"] {0.18.7}[9458]: starting ...
[2012-01-15 21:39:59,012][INFO ][transport ] [Braddock,
Elizabeth "Betsy"] bound_address {inet[/0:0:0:0:0:0:0:0:9300]},
publish_address {inet[/10.190.209.136:9300]}
[2012-01-15 21:40:07,540][INFO ][cluster.service ] [Braddock,
Elizabeth "Betsy"] new_master [Braddock, Elizabeth
"Betsy"][_kMa8HHkQcO2RSEFWJmN6w][inet[/10.190.209.136:9300]], reason:
zen-disco-join (elected_as_master)
[2012-01-15 21:40:07,547][INFO ][discovery ] [Braddock,
Elizabeth "Betsy"] indexcluster/_kMa9JJkQcO2RSEFWJmN7y
[2012-01-15 21:40:07,608][INFO ][http ] [Braddock,
Elizabeth "Betsy"] bound_address {inet[/0:0:0:0:0:0:0:0:9200]},
publish_address {inet[/10.190.215.140:9200]}
[2012-01-15 21:40:07,609][INFO ][node ] [Braddock,
Elizabeth "Betsy"] {0.18.7}[9458]: started
[2012-01-15 21:40:07,702][INFO ][gateway ] [Braddock,
Elizabeth "Betsy"] recovered [0] indices into cluster_state

on the descovery output I don't see ec2 "annotation" at all, what could be
wrong with my configuration ? I did exactly the next , but i didn't
configure the gateway (yet)

cluster.name: es-demo
cloud:
aws:
access_key:
secret_key:
discovery:
type: ec2

2

What do you expect to see? Do you have other nodes in ec2 that will join
this node? If you want more logging info, you can set discovery.ec2 to
TRACE in the logging file.

On Sun, Jan 15, 2012 at 11:45 PM, slavag slavago@gmail.com wrote:

Hi,
I've configured aws ec2 instance as specified in the guide.
But when I'm running bin/elasticsearch -f the output doesn't shows me
that ec2 discovery is actually working and output is next :

[2012-01-15 21:39:52,974][INFO ][node ] [Braddock,
Elizabeth "Betsy"] {0.18.7}[9458]: initializing ...
[2012-01-15 21:39:52,991][INFO ][plugins ] [Braddock,
Elizabeth "Betsy"] loaded [cloud-aws], sites
[2012-01-15 21:39:58,725][INFO ][node ] [Braddock,
Elizabeth "Betsy"] {0.18.7}[9458]: initialized
[2012-01-15 21:39:58,726][INFO ][node ] [Braddock,
Elizabeth "Betsy"] {0.18.7}[9458]: starting ...
[2012-01-15 21:39:59,012][INFO ][transport ] [Braddock,
Elizabeth "Betsy"] bound_address {inet[/0:0:0:0:0:0:0:0:9300]},
publish_address {inet[/10.190.209.136:9300]}
[2012-01-15 21:40:07,540][INFO ][cluster.service ] [Braddock,
Elizabeth "Betsy"] new_master [Braddock, Elizabeth
"Betsy"][_kMa8HHkQcO2RSEFWJmN6w][inet[/10.190.209.136:9300]], reason:
zen-disco-join (elected_as_master)
[2012-01-15 21:40:07,547][INFO ][discovery ] [Braddock,
Elizabeth "Betsy"] indexcluster/_kMa9JJkQcO2RSEFWJmN7y
[2012-01-15 21:40:07,608][INFO ][http ] [Braddock,
Elizabeth "Betsy"] bound_address {inet[/0:0:0:0:0:0:0:0:9200]},
publish_address {inet[/10.190.215.140:9200]}
[2012-01-15 21:40:07,609][INFO ][node ] [Braddock,
Elizabeth "Betsy"] {0.18.7}[9458]: started
[2012-01-15 21:40:07,702][INFO ][gateway ] [Braddock,
Elizabeth "Betsy"] recovered [0] indices into cluster_state

on the descovery output I don't see ec2 "annotation" at all, what could be
wrong with my configuration ? I did exactly the next , but i didn't
configure the gateway (yet)

cluster.name: es-demo
cloud:
aws:
access_key:
secret_key:
discovery:
type: ec2

3

Actually , my fault, I was not aware that in the security group if it's not
added to it-self then servers can't communicate each other within the same
group.

Thank You.

4

Hi,

I'm facing the same problem. Can you please explain what you meant by
"security group added to itself".

Thanks
Rohit

On Monday, January 16, 2012 4:24:16 AM UTC+5:30, slavag wrote:

Actually , my fault, I was not aware that in the security group if it's
not added to it-self then servers can't communicate each other within the
same group.

Thank You.

5

You need to allow the communication from your specific security group to
it-self in the security groups config, otherwise machines in this group
can't communicate with each other within the same group.

On Thursday, June 14, 2012 9:49:08 PM UTC+3, rohit reddy wrote:

Hi,

I'm facing the same problem. Can you please explain what you meant by
"security group added to itself".

Thanks
Rohit

On Monday, January 16, 2012 4:24:16 AM UTC+5:30, slavag wrote:

Actually , my fault, I was not aware that in the security group if it's
not added to it-self then servers can't communicate each other within the
same group.

Thank You.