EC2 discovery issue

classic Classic list List threaded Threaded
29 messages Options
12
Reply | Threaded
Open this post in threaded view
|

EC2 discovery issue

Ridvan Gyundogan
Hi,
I am trying to run 2 ec2 instances according to the following article
http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.

This is my config/elasticsearch.yml:

cluster:
  name: perftests

discovery:
    type: ec2

cloud:
    aws:
        access_key: XXXXXXXXX
        secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

and this is my log on both ec2 nodes no matter which one I start
first:
[2011-07-04 20:11:34,732][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initializing ...
[2011-07-04 20:11:34,741][INFO ][plugins                  ] [Fusion]
loaded [cloud-aws]
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initialized
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: starting ...
[2011-07-04 20:11:38,974][INFO ][transport                ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.234.149.155:9300]}
[2011-07-04 20:11:46,324][INFO ][cluster.service          ] [Fusion]
new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
10.234.149.155:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-04 20:11:46,361][INFO ][discovery                ] [Fusion]
perftests/1Mq8yU1hQJWmO_7ubqNt5A
[2011-07-04 20:11:46,391][INFO ][gateway                  ] [Fusion]
recovered [0] indices into cluster_state
[2011-07-04 20:11:46,395][INFO ][http                     ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.234.149.155:9200]}
[2011-07-04 20:11:46,396][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: started

Why are they not able to find each other and run as a cluster?
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Paul Loy
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}

On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <[hidden email]> wrote:
Hi,
I am trying to run 2 ec2 instances according to the following article
http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.

This is my config/elasticsearch.yml:

cluster:
 name: perftests

discovery:
   type: ec2

cloud:
   aws:
       access_key: XXXXXXXXX
       secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

and this is my log on both ec2 nodes no matter which one I start
first:
[2011-07-04 20:11:34,732][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initializing ...
[2011-07-04 20:11:34,741][INFO ][plugins                  ] [Fusion]
loaded [cloud-aws]
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initialized
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: starting ...
[2011-07-04 20:11:38,974][INFO ][transport                ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.234.149.155:9300]}
[2011-07-04 20:11:46,324][INFO ][cluster.service          ] [Fusion]
new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
10.234.149.155:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-04 20:11:46,361][INFO ][discovery                ] [Fusion]
perftests/1Mq8yU1hQJWmO_7ubqNt5A
[2011-07-04 20:11:46,391][INFO ][gateway                  ] [Fusion]
recovered [0] indices into cluster_state
[2011-07-04 20:11:46,395][INFO ][http                     ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.234.149.155:9200]}
[2011-07-04 20:11:46,396][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: started

Why are they not able to find each other and run as a cluster?



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Paul Loy
You also need to specify IP addresses as the EC2 plugin searches other instances by their private IPv4 address.

On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email]> wrote:
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}

On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <[hidden email]> wrote:
Hi,
I am trying to run 2 ec2 instances according to the following article
http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.

This is my config/elasticsearch.yml:

cluster:
 name: perftests

discovery:
   type: ec2

cloud:
   aws:
       access_key: XXXXXXXXX
       secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

and this is my log on both ec2 nodes no matter which one I start
first:
[2011-07-04 20:11:34,732][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initializing ...
[2011-07-04 20:11:34,741][INFO ][plugins                  ] [Fusion]
loaded [cloud-aws]
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initialized
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: starting ...
[2011-07-04 20:11:38,974][INFO ][transport                ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.234.149.155:9300]}
[2011-07-04 20:11:46,324][INFO ][cluster.service          ] [Fusion]
new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
10.234.149.155:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-04 20:11:46,361][INFO ][discovery                ] [Fusion]
perftests/1Mq8yU1hQJWmO_7ubqNt5A
[2011-07-04 20:11:46,391][INFO ][gateway                  ] [Fusion]
recovered [0] indices into cluster_state
[2011-07-04 20:11:46,395][INFO ][http                     ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.234.149.155:9200]}
[2011-07-04 20:11:46,396][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: started

Why are they not able to find each other and run as a cluster?



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Karl Baum
If we specify ip addresses, there probably is no advantage over zen discovery.  

I vaguely remember that on head you don't need ip addresses for ec2 discovery.  Is that correct?

Thx

Sent from my iPhone

On Jul 4, 2011, at 5:01 PM, Paul Loy <[hidden email]> wrote:

You also need to specify IP addresses as the EC2 plugin searches other instances by their private IPv4 address.

On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email]> wrote:
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}

On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <[hidden email]> wrote:
Hi,
I am trying to run 2 ec2 instances according to the following article
http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.

This is my config/elasticsearch.yml:

cluster:
 name: perftests

discovery:
   type: ec2

cloud:
   aws:
       access_key: XXXXXXXXX
       secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

and this is my log on both ec2 nodes no matter which one I start
first:
[2011-07-04 20:11:34,732][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initializing ...
[2011-07-04 20:11:34,741][INFO ][plugins                  ] [Fusion]
loaded [cloud-aws]
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initialized
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: starting ...
[2011-07-04 20:11:38,974][INFO ][transport                ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.234.149.155:9300]}
[2011-07-04 20:11:46,324][INFO ][cluster.service          ] [Fusion]
new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
10.234.149.155:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-04 20:11:46,361][INFO ][discovery                ] [Fusion]
perftests/1Mq8yU1hQJWmO_7ubqNt5A
[2011-07-04 20:11:46,391][INFO ][gateway                  ] [Fusion]
recovered [0] indices into cluster_state
[2011-07-04 20:11:46,395][INFO ][http                     ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.234.149.155:9200]}
[2011-07-04 20:11:46,396][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: started

Why are they not able to find each other and run as a cluster?



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Paul Loy
Yeah, in master you can use _ec2_ and it'll use the private ipv4.

On Mon, Jul 4, 2011 at 10:59 PM, Karl Baum <[hidden email]> wrote:
If we specify ip addresses, there probably is no advantage over zen discovery.  

I vaguely remember that on head you don't need ip addresses for ec2 discovery.  Is that correct?

Thx

Sent from my iPhone

On Jul 4, 2011, at 5:01 PM, Paul Loy <[hidden email]> wrote:

You also need to specify IP addresses as the EC2 plugin searches other instances by their private IPv4 address.

On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email][hidden email]> wrote:
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}

On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <[hidden email][hidden email]> wrote:
Hi,
I am trying to run 2 ec2 instances according to the following article
http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.

This is my config/elasticsearch.yml:

cluster:
 name: perftests

discovery:
   type: ec2

cloud:
   aws:
       access_key: XXXXXXXXX
       secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

and this is my log on both ec2 nodes no matter which one I start
first:
[2011-07-04 20:11:34,732][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initializing ...
[2011-07-04 20:11:34,741][INFO ][plugins                  ] [Fusion]
loaded [cloud-aws]
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initialized
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: starting ...
[2011-07-04 20:11:38,974][INFO ][transport                ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.234.149.155:9300]}
[2011-07-04 20:11:46,324][INFO ][cluster.service          ] [Fusion]
new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
10.234.149.155:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-04 20:11:46,361][INFO ][discovery                ] [Fusion]
perftests/1Mq8yU1hQJWmO_7ubqNt5A
[2011-07-04 20:11:46,391][INFO ][gateway                  ] [Fusion]
recovered [0] indices into cluster_state
[2011-07-04 20:11:46,395][INFO ][http                     ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.234.149.155:9200]}
[2011-07-04 20:11:46,396][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: started

Why are they not able to find each other and run as a cluster?



--
---------------------------------------------
Paul Loy
[hidden email][hidden email]
http://uk.linkedin.com/in/paulloy



--
---------------------------------------------
Paul Loy
[hidden email][hidden email]
http://uk.linkedin.com/in/paulloy



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

kimchy
Administrator
Even without master (where you just say _ec2_), most cloud platform have common network interfaces names, and you can still use a single configuration file by providing the network interface name (check the network settings docs).

On Tuesday, July 5, 2011 at 1:37 AM, Paul Loy wrote:

Yeah, in master you can use _ec2_ and it'll use the private ipv4.

On Mon, Jul 4, 2011 at 10:59 PM, Karl Baum <[hidden email]> wrote:
If we specify ip addresses, there probably is no advantage over zen discovery.  

I vaguely remember that on head you don't need ip addresses for ec2 discovery.  Is that correct?

Thx

Sent from my iPhone

On Jul 4, 2011, at 5:01 PM, Paul Loy <[hidden email]> wrote:

You also need to specify IP addresses as the EC2 plugin searches other instances by their private IPv4 address.

On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email][hidden email]> wrote:
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}

On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <[hidden email][hidden email]> wrote:
Hi,
I am trying to run 2 ec2 instances according to the following article
http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.

This is my config/elasticsearch.yml:

cluster:
 name: perftests

discovery:
   type: ec2

cloud:
   aws:
       access_key: XXXXXXXXX
       secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

and this is my log on both ec2 nodes no matter which one I start
first:
[2011-07-04 20:11:34,732][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initializing ...
[2011-07-04 20:11:34,741][INFO ][plugins                  ] [Fusion]
loaded [cloud-aws]
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: initialized
[2011-07-04 20:11:38,868][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: starting ...
[2011-07-04 20:11:38,974][INFO ][transport                ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
10.234.149.155:9300]}
[2011-07-04 20:11:46,324][INFO ][cluster.service          ] [Fusion]
new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
10.234.149.155:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-04 20:11:46,361][INFO ][discovery                ] [Fusion]
perftests/1Mq8yU1hQJWmO_7ubqNt5A
[2011-07-04 20:11:46,391][INFO ][gateway                  ] [Fusion]
recovered [0] indices into cluster_state
[2011-07-04 20:11:46,395][INFO ][http                     ] [Fusion]
bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
10.234.149.155:9200]}
[2011-07-04 20:11:46,396][INFO ][node                     ] [Fusion]
{elasticsearch/0.16.2}[1223]: started

Why are they not able to find each other and run as a cluster?



--
---------------------------------------------
Paul Loy
[hidden email][hidden email]
http://uk.linkedin.com/in/paulloy



--
---------------------------------------------
Paul Loy
[hidden email][hidden email]
http://uk.linkedin.com/in/paulloy



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy

Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Ridvan Gyundogan
Thanks to all, but I still don't completely get it:
1. Where should I put _ec2_ ?
2. Do I need to add something else except _ec2_ to my config/
elasticsearch.yml file?

On Jul 5, 1:57 pm, Shay Banon <[hidden email]> wrote:

> Even without master (where you just say _ec2_), most cloud platform have common network interfaces names, and you can still use a single configuration file by providing the network interface name (check the network settings docs).
>
>
>
>
>
>
>
> On Tuesday, July 5, 2011 at 1:37 AM, Paul Loy wrote:
> > Yeah, in master you can use _ec2_ and it'll use the private ipv4.
>
> > On Mon, Jul 4, 2011 at 10:59 PM, Karl Baum <[hidden email] (mailto:[hidden email])> wrote:
> > > If we specify ip addresses, there probably is no advantage over zen discovery.
>
> > > I vaguely remember that on head you don't need ip addresses for ec2 discovery. Is that correct?
>
> > > Thx
>
> > > Sent from my iPhone
>
> > > On Jul 4, 2011, at 5:01 PM, Paul Loy <[hidden email] (mailto:[hidden email])> wrote:
>
> > > > You also need to specify IP addresses as the EC2 plugin searches other instances by their private IPv4 address.
>
> > > > On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email] (mailto:[hidden email])> wrote:
> > > > > bound_address {inet[/0:0:0:0:0:0:0:0:9300]}
>
> > > > >  On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <[hidden email] (mailto:[hidden email])> wrote:
> > > > > > Hi,
> > > > > >  I am trying to run 2 ec2 instances according to the following article
> > > > > >http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.
>
> > > > > >  This is my config/elasticsearch.yml:
>
> > > > > >  cluster:
> > > > > > name: perftests
>
> > > > > >  discovery:
> > > > > > type: ec2
>
> > > > > >  cloud:
> > > > > > aws:
> > > > > > access_key: XXXXXXXXX
> > > > > > secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > > > > >  and this is my log on both ec2 nodes no matter which one I start
> > > > > >  first:
> > > > > >  [2011-07-04 20:11:34,732][INFO ][node  ] [Fusion]
> > > > > >  {elasticsearch/0.16.2}[1223]: initializing ...
> > > > > >  [2011-07-04 20:11:34,741][INFO ][plugins ] [Fusion]
> > > > > >  loaded [cloud-aws]
> > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > >  {elasticsearch/0.16.2}[1223]: initialized
> > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > >  {elasticsearch/0.16.2}[1223]: starting ...
> > > > > >  [2011-07-04 20:11:38,974][INFO ][transport ] [Fusion]
> > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
> > > > > > 10.234.149.155:9300 (http://10.234.149.155:9300)]}
> > > > > >  [2011-07-04 20:11:46,324][INFO ][cluster.service ] [Fusion]
> > > > > >  new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
> > > > > >  10.234.149.155:9300]], reason: zen-disco-join (elected_as_master)
> > > > > >  [2011-07-04 20:11:46,361][INFO ][discovery ] [Fusion]
> > > > > >  perftests/1Mq8yU1hQJWmO_7ubqNt5A
> > > > > >  [2011-07-04 20:11:46,391][INFO ][gateway ] [Fusion]
> > > > > >  recovered [0] indices into cluster_state
> > > > > >  [2011-07-04 20:11:46,395][INFO ][http  ] [Fusion]
> > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
> > > > > > 10.234.149.155:9200 (http://10.234.149.155:9200)]}
> > > > > >  [2011-07-04 20:11:46,396][INFO ][node  ] [Fusion]
> > > > > >  {elasticsearch/0.16.2}[1223]: started
>
> > > > > >  Why are they not able to find each other and run as a cluster?
>
> > > > > --
> > > > > ---------------------------------------------
> > > > > Paul Loy
> > > > > [hidden email] (mailto:[hidden email])
> > > > >http://uk.linkedin.com/in/paulloy
>
> > > > --
> > > > ---------------------------------------------
> > > > Paul Loy
> > > > [hidden email] (mailto:[hidden email])
> > > >http://uk.linkedin.com/in/paulloy
>
> > --
> > ---------------------------------------------
> > Paul Loy
> > [hidden email] (mailto:[hidden email])
> >http://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Ridvan Gyundogan
I added the following to my elasticsearch.yml and now I am not bound
to 0.0.0.0:
network:
    bind_host: _non_loopback:ipv4_

And the log of the second node now looks like this:
[2011-07-05 12:05:50,944][INFO ][node                     ]
[Powderkeg] {elasticsearch/0.16.2}[988]: initializing ...
[2011-07-05 12:05:50,966][INFO ][plugins                  ]
[Powderkeg] loaded [cloud-aws]
[2011-07-05 12:05:55,795][INFO ][node                     ]
[Powderkeg] {elasticsearch/0.16.2}[988]: initialized
[2011-07-05 12:05:55,796][INFO ][node                     ]
[Powderkeg] {elasticsearch/0.16.2}[988]: starting ...
[2011-07-05 12:05:55,929][INFO ][transport                ]
[Powderkeg] bound_address {inet[/10.234.189.8:9300]}, publish_address
{inet[/10.234.189.8:9300]}
[2011-07-05 12:06:00,819][INFO ][cluster.service          ]
[Powderkeg] new_master [Powderkeg][9GIGXIA4Tf6jBEWT7TpG9A][inet[/
10.234.189.8:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-05 12:06:00,859][INFO ][discovery                ]
[Powderkeg] perftests/9GIGXIA4Tf6jBEWT7TpG9A
[2011-07-05 12:06:00,913][INFO ][gateway                  ]
[Powderkeg] recovered [0] indices into cluster_state
[2011-07-05 12:06:00,914][INFO ][http                     ]
[Powderkeg] bound_address {inet[/10.234.189.8:9200]}, publish_address
{inet[/10.234.189.8:9200]}
[2011-07-05 12:06:00,914][INFO ][node                     ]
[Powderkeg] {elasticsearch/0.16.2}[988]: started


but still it doesn't find the master.
Any ideas?



On Jul 5, 2:32 pm, Ridvan Gyundogan <[hidden email]> wrote:

> Thanks to all, but I still don't completely get it:
> 1. Where should I put _ec2_ ?
> 2. Do I need to add something else except _ec2_ to my config/
> elasticsearch.yml file?
>
> On Jul 5, 1:57 pm, Shay Banon <[hidden email]> wrote:
>
>
>
>
>
>
>
> > Even without master (where you just say _ec2_), most cloud platform have common network interfaces names, and you can still use a single configuration file by providing the network interface name (check the network settings docs).
>
> > On Tuesday, July 5, 2011 at 1:37 AM, Paul Loy wrote:
> > > Yeah, in master you can use _ec2_ and it'll use the private ipv4.
>
> > > On Mon, Jul 4, 2011 at 10:59 PM, Karl Baum <[hidden email] (mailto:[hidden email])> wrote:
> > > > If we specify ip addresses, there probably is no advantage over zen discovery.
>
> > > > I vaguely remember that on head you don't need ip addresses for ec2 discovery. Is that correct?
>
> > > > Thx
>
> > > > Sent from my iPhone
>
> > > > On Jul 4, 2011, at 5:01 PM, Paul Loy <[hidden email] (mailto:[hidden email])> wrote:
>
> > > > > You also need to specify IP addresses as the EC2 plugin searches other instances by their private IPv4 address.
>
> > > > > On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email] (mailto:[hidden email])> wrote:
> > > > > > bound_address {inet[/0:0:0:0:0:0:0:0:9300]}
>
> > > > > >  On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <[hidden email] (mailto:[hidden email])> wrote:
> > > > > > > Hi,
> > > > > > >  I am trying to run 2 ec2 instances according to the following article
> > > > > > >http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.
>
> > > > > > >  This is my config/elasticsearch.yml:
>
> > > > > > >  cluster:
> > > > > > > name: perftests
>
> > > > > > >  discovery:
> > > > > > > type: ec2
>
> > > > > > >  cloud:
> > > > > > > aws:
> > > > > > > access_key: XXXXXXXXX
> > > > > > > secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > > > > > >  and this is my log on both ec2 nodes no matter which one I start
> > > > > > >  first:
> > > > > > >  [2011-07-04 20:11:34,732][INFO ][node  ] [Fusion]
> > > > > > >  {elasticsearch/0.16.2}[1223]: initializing ...
> > > > > > >  [2011-07-04 20:11:34,741][INFO ][plugins ] [Fusion]
> > > > > > >  loaded [cloud-aws]
> > > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > > >  {elasticsearch/0.16.2}[1223]: initialized
> > > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > > >  {elasticsearch/0.16.2}[1223]: starting ...
> > > > > > >  [2011-07-04 20:11:38,974][INFO ][transport ] [Fusion]
> > > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
> > > > > > > 10.234.149.155:9300 (http://10.234.149.155:9300)]}
> > > > > > >  [2011-07-04 20:11:46,324][INFO ][cluster.service ] [Fusion]
> > > > > > >  new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
> > > > > > >  10.234.149.155:9300]], reason: zen-disco-join (elected_as_master)
> > > > > > >  [2011-07-04 20:11:46,361][INFO ][discovery ] [Fusion]
> > > > > > >  perftests/1Mq8yU1hQJWmO_7ubqNt5A
> > > > > > >  [2011-07-04 20:11:46,391][INFO ][gateway ] [Fusion]
> > > > > > >  recovered [0] indices into cluster_state
> > > > > > >  [2011-07-04 20:11:46,395][INFO ][http  ] [Fusion]
> > > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
> > > > > > > 10.234.149.155:9200 (http://10.234.149.155:9200)]}
> > > > > > >  [2011-07-04 20:11:46,396][INFO ][node  ] [Fusion]
> > > > > > >  {elasticsearch/0.16.2}[1223]: started
>
> > > > > > >  Why are they not able to find each other and run as a cluster?
>
> > > > > > --
> > > > > > ---------------------------------------------
> > > > > > Paul Loy
> > > > > > [hidden email] (mailto:[hidden email])
> > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > > --
> > > > > ---------------------------------------------
> > > > > Paul Loy
> > > > > [hidden email] (mailto:[hidden email])
> > > > >http://uk.linkedin.com/in/paulloy
>
> > > --
> > > ---------------------------------------------
> > > Paul Loy
> > > [hidden email] (mailto:[hidden email])
> > >http://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Paul Loy
network:
   bind_host: _ec2_

?

On Tue, Jul 5, 2011 at 1:14 PM, Ridvan Gyundogan <[hidden email]> wrote:
I added the following to my elasticsearch.yml and now I am not bound
to 0.0.0.0:
network:
   bind_host: _non_loopback:ipv4_

And the log of the second node now looks like this:
[2011-07-05 12:05:50,944][INFO ][node                     ]
[Powderkeg] {elasticsearch/0.16.2}[988]: initializing ...
[2011-07-05 12:05:50,966][INFO ][plugins                  ]
[Powderkeg] loaded [cloud-aws]
[2011-07-05 12:05:55,795][INFO ][node                     ]
[Powderkeg] {elasticsearch/0.16.2}[988]: initialized
[2011-07-05 12:05:55,796][INFO ][node                     ]
[Powderkeg] {elasticsearch/0.16.2}[988]: starting ...
[2011-07-05 12:05:55,929][INFO ][transport                ]
[Powderkeg] bound_address {inet[/10.234.189.8:9300]}, publish_address
{inet[/10.234.189.8:9300]}
[2011-07-05 12:06:00,819][INFO ][cluster.service          ]
[Powderkeg] new_master [Powderkeg][9GIGXIA4Tf6jBEWT7TpG9A][inet[/
10.234.189.8:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-05 12:06:00,859][INFO ][discovery                ]
[Powderkeg] perftests/9GIGXIA4Tf6jBEWT7TpG9A
[2011-07-05 12:06:00,913][INFO ][gateway                  ]
[Powderkeg] recovered [0] indices into cluster_state
[2011-07-05 12:06:00,914][INFO ][http                     ]
[Powderkeg] bound_address {inet[/10.234.189.8:9200]}, publish_address
{inet[/10.234.189.8:9200]}
[2011-07-05 12:06:00,914][INFO ][node                     ]
[Powderkeg] {elasticsearch/0.16.2}[988]: started


but still it doesn't find the master.
Any ideas?



On Jul 5, 2:32 pm, Ridvan Gyundogan <[hidden email]> wrote:
> Thanks to all, but I still don't completely get it:
> 1. Where should I put _ec2_ ?
> 2. Do I need to add something else except _ec2_ to my config/
> elasticsearch.yml file?
>
> On Jul 5, 1:57 pm, Shay Banon <[hidden email]> wrote:
>
>
>
>
>
>
>
> > Even without master (where you just say _ec2_), most cloud platform have common network interfaces names, and you can still use a single configuration file by providing the network interface name (check the network settings docs).
>
> > On Tuesday, July 5, 2011 at 1:37 AM, Paul Loy wrote:
> > > Yeah, in master you can use _ec2_ and it'll use the private ipv4.
>
> > > On Mon, Jul 4, 2011 at 10:59 PM, Karl Baum <[hidden email] (mailto:[hidden email])> wrote:
> > > > If we specify ip addresses, there probably is no advantage over zen discovery.
>
> > > > I vaguely remember that on head you don't need ip addresses for ec2 discovery. Is that correct?
>
> > > > Thx
>
> > > > Sent from my iPhone
>
> > > > On Jul 4, 2011, at 5:01 PM, Paul Loy <[hidden email] (mailto:[hidden email])> wrote:
>
> > > > > You also need to specify IP addresses as the EC2 plugin searches other instances by their private IPv4 address.
>
> > > > > On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email] (mailto:[hidden email])> wrote:
> > > > > > bound_address {inet[/0:0:0:0:0:0:0:0:9300]}
>
> > > > > >  On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <[hidden email] (mailto:[hidden email])> wrote:
> > > > > > > Hi,
> > > > > > >  I am trying to run 2 ec2 instances according to the following article
> > > > > > >http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.
>
> > > > > > >  This is my config/elasticsearch.yml:
>
> > > > > > >  cluster:
> > > > > > > name: perftests
>
> > > > > > >  discovery:
> > > > > > > type: ec2
>
> > > > > > >  cloud:
> > > > > > > aws:
> > > > > > > access_key: XXXXXXXXX
> > > > > > > secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > > > > > >  and this is my log on both ec2 nodes no matter which one I start
> > > > > > >  first:
> > > > > > >  [2011-07-04 20:11:34,732][INFO ][node  ] [Fusion]
> > > > > > >  {elasticsearch/0.16.2}[1223]: initializing ...
> > > > > > >  [2011-07-04 20:11:34,741][INFO ][plugins ] [Fusion]
> > > > > > >  loaded [cloud-aws]
> > > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > > >  {elasticsearch/0.16.2}[1223]: initialized
> > > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > > >  {elasticsearch/0.16.2}[1223]: starting ...
> > > > > > >  [2011-07-04 20:11:38,974][INFO ][transport ] [Fusion]
> > > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address {inet[/
> > > > > > > 10.234.149.155:9300 (http://10.234.149.155:9300)]}
> > > > > > >  [2011-07-04 20:11:46,324][INFO ][cluster.service ] [Fusion]
> > > > > > >  new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
> > > > > > >  10.234.149.155:9300]], reason: zen-disco-join (elected_as_master)
> > > > > > >  [2011-07-04 20:11:46,361][INFO ][discovery ] [Fusion]
> > > > > > >  perftests/1Mq8yU1hQJWmO_7ubqNt5A
> > > > > > >  [2011-07-04 20:11:46,391][INFO ][gateway ] [Fusion]
> > > > > > >  recovered [0] indices into cluster_state
> > > > > > >  [2011-07-04 20:11:46,395][INFO ][http  ] [Fusion]
> > > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address {inet[/
> > > > > > > 10.234.149.155:9200 (http://10.234.149.155:9200)]}
> > > > > > >  [2011-07-04 20:11:46,396][INFO ][node  ] [Fusion]
> > > > > > >  {elasticsearch/0.16.2}[1223]: started
>
> > > > > > >  Why are they not able to find each other and run as a cluster?
>
> > > > > > --
> > > > > > ---------------------------------------------
> > > > > > Paul Loy
> > > > > > [hidden email] (mailto:[hidden email])
> > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > > --
> > > > > ---------------------------------------------
> > > > > Paul Loy
> > > > > [hidden email] (mailto:[hidden email])
> > > > >http://uk.linkedin.com/in/paulloy
>
> > > --
> > > ---------------------------------------------
> > > Paul Loy
> > > [hidden email] (mailto:[hidden email])
> > >http://uk.linkedin.com/in/paulloy



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Ridvan Gyundogan
Hi Paul thanks for your help, I still have an issue.
Now I get:
{elasticsearch/0.16.2}: Startup Failed ...
- BindTransportException[Failed to resolve host [null]]
        IOException[Failed to find network interface for [_ec2_]]

To summarize my elasticsearch.yml now looks like the following:
cluster:
  name: perftests
discovery:
    type: ec2
cloud:
    aws:
        access_key: XXXXXX
        secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

network:
    bind_host: _ec2_




On Jul 5, 3:26 pm, Paul Loy <[hidden email]> wrote:

> network:
>    bind_host: _ec2_
>
> ?
>
>
>
> On Tue, Jul 5, 2011 at 1:14 PM, Ridvan Gyundogan <[hidden email]> wrote:
> > I added the following to my elasticsearch.yml and now I am not bound
> > to 0.0.0.0:
> > network:
> >    bind_host: _non_loopback:ipv4_
>
> > And the log of the second node now looks like this:
> > [2011-07-05 12:05:50,944][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: initializing ...
> > [2011-07-05 12:05:50,966][INFO ][plugins                  ]
> > [Powderkeg] loaded [cloud-aws]
> > [2011-07-05 12:05:55,795][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: initialized
> > [2011-07-05 12:05:55,796][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: starting ...
> > [2011-07-05 12:05:55,929][INFO ][transport                ]
> > [Powderkeg] bound_address {inet[/10.234.189.8:9300]}, publish_address
> > {inet[/10.234.189.8:9300]}
> > [2011-07-05 12:06:00,819][INFO ][cluster.service          ]
> > [Powderkeg] new_master [Powderkeg][9GIGXIA4Tf6jBEWT7TpG9A][inet[/
> > 10.234.189.8:9300]], reason: zen-disco-join (elected_as_master)
> > [2011-07-05 12:06:00,859][INFO ][discovery                ]
> > [Powderkeg] perftests/9GIGXIA4Tf6jBEWT7TpG9A
> > [2011-07-05 12:06:00,913][INFO ][gateway                  ]
> > [Powderkeg] recovered [0] indices into cluster_state
> > [2011-07-05 12:06:00,914][INFO ][http                     ]
> > [Powderkeg] bound_address {inet[/10.234.189.8:9200]}, publish_address
> > {inet[/10.234.189.8:9200]}
> > [2011-07-05 12:06:00,914][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: started
>
> > but still it doesn't find the master.
> > Any ideas?
>
> > On Jul 5, 2:32 pm, Ridvan Gyundogan <[hidden email]> wrote:
> > > Thanks to all, but I still don't completely get it:
> > > 1. Where should I put _ec2_ ?
> > > 2. Do I need to add something else except _ec2_ to my config/
> > > elasticsearch.yml file?
>
> > > On Jul 5, 1:57 pm, Shay Banon <[hidden email]> wrote:
>
> > > > Even without master (where you just say _ec2_), most cloud platform
> > have common network interfaces names, and you can still use a single
> > configuration file by providing the network interface name (check the
> > network settings docs).
>
> > > > On Tuesday, July 5, 2011 at 1:37 AM, Paul Loy wrote:
> > > > > Yeah, in master you can use _ec2_ and it'll use the private ipv4.
>
> > > > > On Mon, Jul 4, 2011 at 10:59 PM, Karl Baum <[hidden email](mailto:
> > [hidden email])> wrote:
> > > > > > If we specify ip addresses, there probably is no advantage over zen
> > discovery.
>
> > > > > > I vaguely remember that on head you don't need ip addresses for ec2
> > discovery. Is that correct?
>
> > > > > > Thx
>
> > > > > > Sent from my iPhone
>
> > > > > > On Jul 4, 2011, at 5:01 PM, Paul Loy <[hidden email] (mailto:
> > [hidden email])> wrote:
>
> > > > > > > You also need to specify IP addresses as the EC2 plugin searches
> > other instances by their private IPv4 address.
>
> > > > > > > On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email](mailto:
> > [hidden email])> wrote:
> > > > > > > > bound_address {inet[/0:0:0:0:0:0:0:0:9300]}
>
> > > > > > > >  On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <
> > [hidden email] (mailto:[hidden email])> wrote:
> > > > > > > > > Hi,
> > > > > > > > >  I am trying to run 2 ec2 instances according to the
> > following article
>
> >http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.
>
> > > > > > > > >  This is my config/elasticsearch.yml:
>
> > > > > > > > >  cluster:
> > > > > > > > > name: perftests
>
> > > > > > > > >  discovery:
> > > > > > > > > type: ec2
>
> > > > > > > > >  cloud:
> > > > > > > > > aws:
> > > > > > > > > access_key: XXXXXXXXX
> > > > > > > > > secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > > > > > > > >  and this is my log on both ec2 nodes no matter which one I
> > start
> > > > > > > > >  first:
> > > > > > > > >  [2011-07-04 20:11:34,732][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: initializing ...
> > > > > > > > >  [2011-07-04 20:11:34,741][INFO ][plugins ] [Fusion]
> > > > > > > > >  loaded [cloud-aws]
> > > > > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: initialized
> > > > > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: starting ...
> > > > > > > > >  [2011-07-04 20:11:38,974][INFO ][transport ] [Fusion]
> > > > > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address
> > {inet[/
> > > > > > > > > 10.234.149.155:9300 (http://10.234.149.155:9300)]}
> > > > > > > > >  [2011-07-04 20:11:46,324][INFO ][cluster.service ] [Fusion]
> > > > > > > > >  new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
> > > > > > > > >  10.234.149.155:9300]], reason: zen-disco-join
> > (elected_as_master)
> > > > > > > > >  [2011-07-04 20:11:46,361][INFO ][discovery ] [Fusion]
> > > > > > > > >  perftests/1Mq8yU1hQJWmO_7ubqNt5A
> > > > > > > > >  [2011-07-04 20:11:46,391][INFO ][gateway ] [Fusion]
> > > > > > > > >  recovered [0] indices into cluster_state
> > > > > > > > >  [2011-07-04 20:11:46,395][INFO ][http  ] [Fusion]
> > > > > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address
> > {inet[/
> > > > > > > > > 10.234.149.155:9200 (http://10.234.149.155:9200)]}
> > > > > > > > >  [2011-07-04 20:11:46,396][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: started
>
> > > > > > > > >  Why are they not able to find each other and run as a
> > cluster?
>
> > > > > > > > --
> > > > > > > > ---------------------------------------------
> > > > > > > > Paul Loy
> > > > > > > > [hidden email] (mailto:[hidden email])
> > > > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > > > > --
> > > > > > > ---------------------------------------------
> > > > > > > Paul Loy
> > > > > > > [hidden email] (mailto:[hidden email])
> > > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > > --
> > > > > ---------------------------------------------
> > > > > Paul Loy
> > > > > [hidden email] (mailto:[hidden email])
> > > > >http://uk.linkedin.com/in/paulloy
>
> --
> ---------------------------------------------
> Paul Loy
> [hidden email]://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Paul Loy
Is this with master? I think that should be 0.17.0 not 0.16.2

On Tue, Jul 5, 2011 at 3:58 PM, Ridvan Gyundogan <[hidden email]> wrote:
Hi Paul thanks for your help, I still have an issue.
Now I get:
{elasticsearch/0.16.2}: Startup Failed ...
- BindTransportException[Failed to resolve host [null]]
       IOException[Failed to find network interface for [_ec2_]]

To summarize my elasticsearch.yml now looks like the following:
cluster:
 name: perftests
discovery:
   type: ec2
cloud:
   aws:
       access_key: XXXXXX
       secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

network:
   bind_host: _ec2_




On Jul 5, 3:26 pm, Paul Loy <[hidden email]> wrote:
> network:
>    bind_host: _ec2_
>
> ?
>
>
>
> On Tue, Jul 5, 2011 at 1:14 PM, Ridvan Gyundogan <[hidden email]> wrote:
> > I added the following to my elasticsearch.yml and now I am not bound
> > to 0.0.0.0:
> > network:
> >    bind_host: _non_loopback:ipv4_
>
> > And the log of the second node now looks like this:
> > [2011-07-05 12:05:50,944][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: initializing ...
> > [2011-07-05 12:05:50,966][INFO ][plugins                  ]
> > [Powderkeg] loaded [cloud-aws]
> > [2011-07-05 12:05:55,795][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: initialized
> > [2011-07-05 12:05:55,796][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: starting ...
> > [2011-07-05 12:05:55,929][INFO ][transport                ]
> > [Powderkeg] bound_address {inet[/10.234.189.8:9300]}, publish_address
> > {inet[/10.234.189.8:9300]}
> > [2011-07-05 12:06:00,819][INFO ][cluster.service          ]
> > [Powderkeg] new_master [Powderkeg][9GIGXIA4Tf6jBEWT7TpG9A][inet[/
> > 10.234.189.8:9300]], reason: zen-disco-join (elected_as_master)
> > [2011-07-05 12:06:00,859][INFO ][discovery                ]
> > [Powderkeg] perftests/9GIGXIA4Tf6jBEWT7TpG9A
> > [2011-07-05 12:06:00,913][INFO ][gateway                  ]
> > [Powderkeg] recovered [0] indices into cluster_state
> > [2011-07-05 12:06:00,914][INFO ][http                     ]
> > [Powderkeg] bound_address {inet[/10.234.189.8:9200]}, publish_address
> > {inet[/10.234.189.8:9200]}
> > [2011-07-05 12:06:00,914][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: started
>
> > but still it doesn't find the master.
> > Any ideas?
>
> > On Jul 5, 2:32 pm, Ridvan Gyundogan <[hidden email]> wrote:
> > > Thanks to all, but I still don't completely get it:
> > > 1. Where should I put _ec2_ ?
> > > 2. Do I need to add something else except _ec2_ to my config/
> > > elasticsearch.yml file?
>
> > > On Jul 5, 1:57 pm, Shay Banon <[hidden email]> wrote:
>
> > > > Even without master (where you just say _ec2_), most cloud platform
> > have common network interfaces names, and you can still use a single
> > configuration file by providing the network interface name (check the
> > network settings docs).
>
> > > > On Tuesday, July 5, 2011 at 1:37 AM, Paul Loy wrote:
> > > > > Yeah, in master you can use _ec2_ and it'll use the private ipv4.
>
> > > > > On Mon, Jul 4, 2011 at 10:59 PM, Karl Baum <[hidden email](mailto:
> > [hidden email])> wrote:
> > > > > > If we specify ip addresses, there probably is no advantage over zen
> > discovery.
>
> > > > > > I vaguely remember that on head you don't need ip addresses for ec2
> > discovery. Is that correct?
>
> > > > > > Thx
>
> > > > > > Sent from my iPhone
>
> > > > > > On Jul 4, 2011, at 5:01 PM, Paul Loy <[hidden email] (mailto:
> > [hidden email])> wrote:
>
> > > > > > > You also need to specify IP addresses as the EC2 plugin searches
> > other instances by their private IPv4 address.
>
> > > > > > > On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email](mailto:
> > [hidden email])> wrote:
> > > > > > > > bound_address {inet[/0:0:0:0:0:0:0:0:9300]}
>
> > > > > > > >  On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <
> > [hidden email] (mailto:[hidden email])> wrote:
> > > > > > > > > Hi,
> > > > > > > > >  I am trying to run 2 ec2 instances according to the
> > following article
>
> >http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.
>
> > > > > > > > >  This is my config/elasticsearch.yml:
>
> > > > > > > > >  cluster:
> > > > > > > > > name: perftests
>
> > > > > > > > >  discovery:
> > > > > > > > > type: ec2
>
> > > > > > > > >  cloud:
> > > > > > > > > aws:
> > > > > > > > > access_key: XXXXXXXXX
> > > > > > > > > secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > > > > > > > >  and this is my log on both ec2 nodes no matter which one I
> > start
> > > > > > > > >  first:
> > > > > > > > >  [2011-07-04 20:11:34,732][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: initializing ...
> > > > > > > > >  [2011-07-04 20:11:34,741][INFO ][plugins ] [Fusion]
> > > > > > > > >  loaded [cloud-aws]
> > > > > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: initialized
> > > > > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: starting ...
> > > > > > > > >  [2011-07-04 20:11:38,974][INFO ][transport ] [Fusion]
> > > > > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address
> > {inet[/
> > > > > > > > > 10.234.149.155:9300 (http://10.234.149.155:9300)]}
> > > > > > > > >  [2011-07-04 20:11:46,324][INFO ][cluster.service ] [Fusion]
> > > > > > > > >  new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
> > > > > > > > >  10.234.149.155:9300]], reason: zen-disco-join
> > (elected_as_master)
> > > > > > > > >  [2011-07-04 20:11:46,361][INFO ][discovery ] [Fusion]
> > > > > > > > >  perftests/1Mq8yU1hQJWmO_7ubqNt5A
> > > > > > > > >  [2011-07-04 20:11:46,391][INFO ][gateway ] [Fusion]
> > > > > > > > >  recovered [0] indices into cluster_state
> > > > > > > > >  [2011-07-04 20:11:46,395][INFO ][http  ] [Fusion]
> > > > > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address
> > {inet[/
> > > > > > > > > 10.234.149.155:9200 (http://10.234.149.155:9200)]}
> > > > > > > > >  [2011-07-04 20:11:46,396][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: started
>
> > > > > > > > >  Why are they not able to find each other and run as a
> > cluster?
>
> > > > > > > > --
> > > > > > > > ---------------------------------------------
> > > > > > > > Paul Loy
> > > > > > > > [hidden email] (mailto:[hidden email])
> > > > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > > > > --
> > > > > > > ---------------------------------------------
> > > > > > > Paul Loy
> > > > > > > [hidden email] (mailto:[hidden email])
> > > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > > --
> > > > > ---------------------------------------------
> > > > > Paul Loy
> > > > > [hidden email] (mailto:[hidden email])
> > > > >http://uk.linkedin.com/in/paulloy
>
> --
> ---------------------------------------------
> Paul Loy
> [hidden email]://uk.linkedin.com/in/paulloy



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

kimchy
Administrator
network.host: _ec2_ is only available in master. Setting to non_loopback is not preferable, you should explicitly use the interface name matching the internal ip.

On Tuesday, July 5, 2011 at 6:12 PM, Paul Loy wrote:

Is this with master? I think that should be 0.17.0 not 0.16.2

On Tue, Jul 5, 2011 at 3:58 PM, Ridvan Gyundogan <[hidden email]> wrote:
Hi Paul thanks for your help, I still have an issue.
Now I get:
{elasticsearch/0.16.2}: Startup Failed ...
- BindTransportException[Failed to resolve host [null]]
       IOException[Failed to find network interface for [_ec2_]]

To summarize my elasticsearch.yml now looks like the following:
cluster:
 name: perftests
discovery:
   type: ec2
cloud:
   aws:
       access_key: XXXXXX
       secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

network:
   bind_host: _ec2_




On Jul 5, 3:26 pm, Paul Loy <[hidden email]> wrote:
> network:
>    bind_host: _ec2_
>
> ?
>
>
>
> On Tue, Jul 5, 2011 at 1:14 PM, Ridvan Gyundogan <[hidden email]> wrote:
> > I added the following to my elasticsearch.yml and now I am not bound
> > to 0.0.0.0:
> > network:
> >    bind_host: _non_loopback:ipv4_
>
> > And the log of the second node now looks like this:
> > [2011-07-05 12:05:50,944][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: initializing ...
> > [2011-07-05 12:05:50,966][INFO ][plugins                  ]
> > [Powderkeg] loaded [cloud-aws]
> > [2011-07-05 12:05:55,795][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: initialized
> > [2011-07-05 12:05:55,796][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: starting ...
> > [2011-07-05 12:05:55,929][INFO ][transport                ]
> > [Powderkeg] bound_address {inet[/10.234.189.8:9300]}, publish_address
> > {inet[/10.234.189.8:9300]}
> > [2011-07-05 12:06:00,819][INFO ][cluster.service          ]
> > [Powderkeg] new_master [Powderkeg][9GIGXIA4Tf6jBEWT7TpG9A][inet[/
> > 10.234.189.8:9300]], reason: zen-disco-join (elected_as_master)
> > [2011-07-05 12:06:00,859][INFO ][discovery                ]
> > [Powderkeg] perftests/9GIGXIA4Tf6jBEWT7TpG9A
> > [2011-07-05 12:06:00,913][INFO ][gateway                  ]
> > [Powderkeg] recovered [0] indices into cluster_state
> > [2011-07-05 12:06:00,914][INFO ][http                     ]
> > [Powderkeg] bound_address {inet[/10.234.189.8:9200]}, publish_address
> > {inet[/10.234.189.8:9200]}
> > [2011-07-05 12:06:00,914][INFO ][node                     ]
> > [Powderkeg] {elasticsearch/0.16.2}[988]: started
>
> > but still it doesn't find the master.
> > Any ideas?
>
> > On Jul 5, 2:32 pm, Ridvan Gyundogan <[hidden email]> wrote:
> > > Thanks to all, but I still don't completely get it:
> > > 1. Where should I put _ec2_ ?
> > > 2. Do I need to add something else except _ec2_ to my config/
> > > elasticsearch.yml file?
>
> > > On Jul 5, 1:57 pm, Shay Banon <[hidden email]> wrote:
>
> > > > Even without master (where you just say _ec2_), most cloud platform
> > have common network interfaces names, and you can still use a single
> > configuration file by providing the network interface name (check the
> > network settings docs).
>
> > > > On Tuesday, July 5, 2011 at 1:37 AM, Paul Loy wrote:
> > > > > Yeah, in master you can use _ec2_ and it'll use the private ipv4.
>
> > > > > On Mon, Jul 4, 2011 at 10:59 PM, Karl Baum <[hidden email](mailto:
> > [hidden email])> wrote:
> > > > > > If we specify ip addresses, there probably is no advantage over zen
> > discovery.
>
> > > > > > I vaguely remember that on head you don't need ip addresses for ec2
> > discovery. Is that correct?
>
> > > > > > Thx
>
> > > > > > Sent from my iPhone
>
> > > > > > On Jul 4, 2011, at 5:01 PM, Paul Loy <[hidden email] (mailto:
> > [hidden email])> wrote:
>
> > > > > > > You also need to specify IP addresses as the EC2 plugin searches
> > other instances by their private IPv4 address.
>
> > > > > > > On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email](mailto:
> > [hidden email])> wrote:
> > > > > > > > bound_address {inet[/0:0:0:0:0:0:0:0:9300]}
>
> > > > > > > >  On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <
> > [hidden email] (mailto:[hidden email])> wrote:
> > > > > > > > > Hi,
> > > > > > > > >  I am trying to run 2 ec2 instances according to the
> > following article
>
> >http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.
>
> > > > > > > > >  This is my config/elasticsearch.yml:
>
> > > > > > > > >  cluster:
> > > > > > > > > name: perftests
>
> > > > > > > > >  discovery:
> > > > > > > > > type: ec2
>
> > > > > > > > >  cloud:
> > > > > > > > > aws:
> > > > > > > > > access_key: XXXXXXXXX
> > > > > > > > > secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > > > > > > > >  and this is my log on both ec2 nodes no matter which one I
> > start
> > > > > > > > >  first:
> > > > > > > > >  [2011-07-04 20:11:34,732][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: initializing ...
> > > > > > > > >  [2011-07-04 20:11:34,741][INFO ][plugins ] [Fusion]
> > > > > > > > >  loaded [cloud-aws]
> > > > > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: initialized
> > > > > > > > >  [2011-07-04 20:11:38,868][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: starting ...
> > > > > > > > >  [2011-07-04 20:11:38,974][INFO ][transport ] [Fusion]
> > > > > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address
> > {inet[/
> > > > > > > > > 10.234.149.155:9300 (http://10.234.149.155:9300)]}
> > > > > > > > >  [2011-07-04 20:11:46,324][INFO ][cluster.service ] [Fusion]
> > > > > > > > >  new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
> > > > > > > > >  10.234.149.155:9300]], reason: zen-disco-join
> > (elected_as_master)
> > > > > > > > >  [2011-07-04 20:11:46,361][INFO ][discovery ] [Fusion]
> > > > > > > > >  perftests/1Mq8yU1hQJWmO_7ubqNt5A
> > > > > > > > >  [2011-07-04 20:11:46,391][INFO ][gateway ] [Fusion]
> > > > > > > > >  recovered [0] indices into cluster_state
> > > > > > > > >  [2011-07-04 20:11:46,395][INFO ][http  ] [Fusion]
> > > > > > > > >  bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address
> > {inet[/
> > > > > > > > > 10.234.149.155:9200 (http://10.234.149.155:9200)]}
> > > > > > > > >  [2011-07-04 20:11:46,396][INFO ][node  ] [Fusion]
> > > > > > > > >  {elasticsearch/0.16.2}[1223]: started
>
> > > > > > > > >  Why are they not able to find each other and run as a
> > cluster?
>
> > > > > > > > --
> > > > > > > > ---------------------------------------------
> > > > > > > > Paul Loy
> > > > > > > > [hidden email] (mailto:[hidden email])
> > > > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > > > > --
> > > > > > > ---------------------------------------------
> > > > > > > Paul Loy
> > > > > > > [hidden email] (mailto:[hidden email])
> > > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > > --
> > > > > ---------------------------------------------
> > > > > Paul Loy
> > > > > [hidden email] (mailto:[hidden email])
> > > > >http://uk.linkedin.com/in/paulloy
>
> --
> ---------------------------------------------
> Paul Loy
> [hidden email]://uk.linkedin.com/in/paulloy



--
---------------------------------------------
Paul Loy
[hidden email]
http://uk.linkedin.com/in/paulloy

Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Ridvan Gyundogan
Hi Shay,
I tried both:
network:
    host: _ec2_
network:
    bind_host: _ec2_

I always get:
Startup Failed ...
- BindTransportException[Failed to resolve host [null]]
        IOException[Failed to find network interface for [_ec2_]]

I start only 1 node at the moment so sure it should be the master.

Any ideas?



On Jul 6, 4:11 am, Shay Banon <[hidden email]> wrote:

> network.host: _ec2_ is only available in master. Setting to non_loopback is not preferable, you should explicitly use the interface name matching the internal ip.
>
>
>
>
>
>
>
> On Tuesday, July 5, 2011 at 6:12 PM, Paul Loy wrote:
> > Is this with master? I think that should be 0.17.0 not 0.16.2
>
> > On Tue, Jul 5, 2011 at 3:58 PM, Ridvan Gyundogan <[hidden email] (mailto:[hidden email])> wrote:
> > > Hi Paul thanks for your help, I still have an issue.
> > >  Now I get:
> > >  {elasticsearch/0.16.2}: Startup Failed ...
> > >  - BindTransportException[Failed to resolve host [null]]
> > > IOException[Failed to find network interface for [_ec2_]]
>
> > >  To summarize my elasticsearch.yml now looks like the following:
> > > cluster:
> > > name: perftests
> > >  discovery:
> > > type: ec2
> > >  cloud:
> > > aws:
> > > access_key: XXXXXX
> > > secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > >  network:
> > > bind_host: _ec2_
>
> > >  On Jul 5, 3:26 pm, Paul Loy <[hidden email] (mailto:[hidden email])> wrote:
> > > > network:
> > > > bind_host: _ec2_
>
> > > > ?
>
> > > > On Tue, Jul 5, 2011 at 1:14 PM, Ridvan Gyundogan <[hidden email] (mailto:[hidden email])> wrote:
> > > > > I added the following to my elasticsearch.yml and now I am not bound
> > > > > to 0.0.0.0 (http://0.0.0.0):
> > > > > network:
> > > > > bind_host: _non_loopback:ipv4_
>
> > > > > And the log of the second node now looks like this:
> > > > > [2011-07-05 12:05:50,944][INFO ][node  ]
> > > > > [Powderkeg] {elasticsearch/0.16.2}[988]: initializing ...
> > > > > [2011-07-05 12:05:50,966][INFO ][plugins ]
> > > > > [Powderkeg] loaded [cloud-aws]
> > > > > [2011-07-05 12:05:55,795][INFO ][node  ]
> > > > > [Powderkeg] {elasticsearch/0.16.2}[988]: initialized
> > > > > [2011-07-05 12:05:55,796][INFO ][node  ]
> > > > > [Powderkeg] {elasticsearch/0.16.2}[988]: starting ...
> > > > > [2011-07-05 12:05:55,929][INFO ][transport ]
> > > > > [Powderkeg] bound_address {inet[/10.234.189.8:9300]}, publish_address
> > > > > {inet[/10.234.189.8:9300 (http://10.234.189.8:9300)]}
> > > > > [2011-07-05 12:06:00,819][INFO ][cluster.service ]
> > > > > [Powderkeg] new_master [Powderkeg][9GIGXIA4Tf6jBEWT7TpG9A][inet[/
> > > > > 10.234.189.8:9300]], reason: zen-disco-join (elected_as_master)
> > > > > [2011-07-05 12:06:00,859][INFO ][discovery ]
> > > > > [Powderkeg] perftests/9GIGXIA4Tf6jBEWT7TpG9A
> > > > > [2011-07-05 12:06:00,913][INFO ][gateway ]
> > > > > [Powderkeg] recovered [0] indices into cluster_state
> > > > > [2011-07-05 12:06:00,914][INFO ][http  ]
> > > > > [Powderkeg] bound_address {inet[/10.234.189.8:9200]}, publish_address
> > > > > {inet[/10.234.189.8:9200 (http://10.234.189.8:9200)]}
> > > > > [2011-07-05 12:06:00,914][INFO ][node  ]
> > > > > [Powderkeg] {elasticsearch/0.16.2}[988]: started
>
> > > > > but still it doesn't find the master.
> > > > > Any ideas?
>
> > > > > On Jul 5, 2:32 pm, Ridvan Gyundogan <[hidden email] (mailto:[hidden email])> wrote:
> > > > > > Thanks to all, but I still don't completely get it:
> > > > > > 1. Where should I put _ec2_ ?
> > > > > > 2. Do I need to add something else except _ec2_ to my config/
> > > > > > elasticsearch.yml file?
>
> > > > > > On Jul 5, 1:57 pm, Shay Banon <[hidden email] (mailto:[hidden email])> wrote:
>
> > > > > > > Even without master (where you just say _ec2_), most cloud platform
> > > > > have common network interfaces names, and you can still use a single
> > > > > configuration file by providing the network interface name (check the
> > > > > network settings docs).
>
> > > > > > > On Tuesday, July 5, 2011 at 1:37 AM, Paul Loy wrote:
> > > > > > > > Yeah, in master you can use _ec2_ and it'll use the private ipv4.
>
> > > > > > > > On Mon, Jul 4, 2011 at 10:59 PM, Karl Baum <[hidden email] (mailto:[hidden email])(mailto:
> > > > > [hidden email] (mailto:[hidden email]))> wrote:
> > > > > > > > > If we specify ip addresses, there probably is no advantage over zen
> > > > > discovery.
>
> > > > > > > > > I vaguely remember that on head you don't need ip addresses for ec2
> > > > > discovery. Is that correct?
>
> > > > > > > > > Thx
>
> > > > > > > > > Sent from my iPhone
>
> > > > > > > > > On Jul 4, 2011, at 5:01 PM, Paul Loy <[hidden email] (mailto:[hidden email]) (mailto:
> > > > > [hidden email] (mailto:[hidden email]))> wrote:
>
> > > > > > > > > > You also need to specify IP addresses as the EC2 plugin searches
> > > > > other instances by their private IPv4 address.
>
> > > > > > > > > > On Mon, Jul 4, 2011 at 9:58 PM, Paul Loy <[hidden email] (mailto:[hidden email])(mailto:
> > > > > [hidden email] (mailto:[hidden email]))> wrote:
> > > > > > > > > > > bound_address {inet[/0:0:0:0:0:0:0:0:9300]}
>
> > > > > > > > > > > On Mon, Jul 4, 2011 at 9:21 PM, Ridvan Gyundogan <
> > > > > [hidden email] (mailto:[hidden email]) (mailto:[hidden email])> wrote:
> > > > > > > > > > > > Hi,
> > > > > > > > > > > > I am trying to run 2 ec2 instances according to the
> > > > > following article
>
> > > > >http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html.
>
> > > > > > > > > > > > This is my config/elasticsearch.yml:
>
> > > > > > > > > > > > cluster:
> > > > > > > > > > > > name: perftests
>
> > > > > > > > > > > > discovery:
> > > > > > > > > > > > type: ec2
>
> > > > > > > > > > > > cloud:
> > > > > > > > > > > > aws:
> > > > > > > > > > > > access_key: XXXXXXXXX
> > > > > > > > > > > > secret_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > > > > > > > > > > > and this is my log on both ec2 nodes no matter which one I
> > > > > start
> > > > > > > > > > > > first:
> > > > > > > > > > > > [2011-07-04 20:11:34,732][INFO ][node ] [Fusion]
> > > > > > > > > > > > {elasticsearch/0.16.2}[1223]: initializing ...
> > > > > > > > > > > > [2011-07-04 20:11:34,741][INFO ][plugins ] [Fusion]
> > > > > > > > > > > > loaded [cloud-aws]
> > > > > > > > > > > > [2011-07-04 20:11:38,868][INFO ][node ] [Fusion]
> > > > > > > > > > > > {elasticsearch/0.16.2}[1223]: initialized
> > > > > > > > > > > > [2011-07-04 20:11:38,868][INFO ][node ] [Fusion]
> > > > > > > > > > > > {elasticsearch/0.16.2}[1223]: starting ...
> > > > > > > > > > > > [2011-07-04 20:11:38,974][INFO ][transport ] [Fusion]
> > > > > > > > > > > > bound_address {inet[/0:0:0:0:0:0:0:0:9300]}, publish_address
> > > > > {inet[/
> > > > > > > > > > > > 10.234.149.155:9300 (http://10.234.149.155:9300) (http://10.234.149.155:9300)]}
> > > > > > > > > > > > [2011-07-04 20:11:46,324][INFO ][cluster.service ] [Fusion]
> > > > > > > > > > > > new_master [Fusion][1Mq8yU1hQJWmO_7ubqNt5A][inet[/
> > > > > > > > > > > > 10.234.149.155:9300]], reason: zen-disco-join
> > > > > (elected_as_master)
> > > > > > > > > > > > [2011-07-04 20:11:46,361][INFO ][discovery ] [Fusion]
> > > > > > > > > > > > perftests/1Mq8yU1hQJWmO_7ubqNt5A
> > > > > > > > > > > > [2011-07-04 20:11:46,391][INFO ][gateway ] [Fusion]
> > > > > > > > > > > > recovered [0] indices into cluster_state
> > > > > > > > > > > > [2011-07-04 20:11:46,395][INFO ][http ] [Fusion]
> > > > > > > > > > > > bound_address {inet[/0:0:0:0:0:0:0:0:9200]}, publish_address
> > > > > {inet[/
> > > > > > > > > > > > 10.234.149.155:9200 (http://10.234.149.155:9200) (http://10.234.149.155:9200)]}
> > > > > > > > > > > > [2011-07-04 20:11:46,396][INFO ][node ] [Fusion]
> > > > > > > > > > > > {elasticsearch/0.16.2}[1223]: started
>
> > > > > > > > > > > > Why are they not able to find each other and run as a
> > > > > cluster?
>
> > > > > > > > > > > --
> > > > > > > > > > > ---------------------------------------------
> > > > > > > > > > > Paul Loy
> > > > > > > > > > > [hidden email] (mailto:[hidden email]) (mailto:[hidden email])
> > > > > > > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > > > > > > > --
> > > > > > > > > > ---------------------------------------------
> > > > > > > > > > Paul Loy
> > > > > > > > > > [hidden email] (mailto:[hidden email]) (mailto:[hidden email])
> > > > > > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > > > > > --
> > > > > > > > ---------------------------------------------
> > > > > > > > Paul Loy
> > > > > > > > [hidden email] (mailto:[hidden email]) (mailto:[hidden email])
> > > > > > > >http://uk.linkedin.com/in/paulloy
>
> > > > --
> > > > ---------------------------------------------
> > > > Paul Loy
> > > > [hidden email]://uk.linkedin.com/in/paulloy
>
> > --
> > ---------------------------------------------
> > Paul Loy
> > [hidden email] (mailto:[hidden email])
> >http://uk.linkedin.com/in/paulloy
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Clinton Gormley

> I start only 1 node at the moment so sure it should be the master.
>

By master, Shay means the version of ElasticSearch that is currently
master on github, not a released version.

You need to download and compile it yourself:

http://www.elasticsearch.org/download/master/

clint

Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Ridvan Gyundogan
Ah ok thanks I will try. 


On Wed, Jul 6, 2011 at 2:37 PM, Clinton Gormley <[hidden email]> wrote:

> I start only 1 node at the moment so sure it should be the master.
>

By master, Shay means the version of ElasticSearch that is currently
master on github, not a released version.

You need to download and compile it yourself:

http://www.elasticsearch.org/download/master/

clint


Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Ridvan Gyundogan
Unfortunately using the trunk is not an option at the moment because
there are some maven dependencies to the 16.2 jar in our project.
 We will upgrade to 0.17 once it is officially released.

Now I tried the "Zen" as described here:
http://www.elasticsearch.org/blog/2010/05/11/here-comes-the-cloud.html

my elasticsearch.yml on the slave looks like this:
cluster:
  name: perftests

discovery:
    type: cloud
    zen:
        ping_timeout: 30s
cloud:
    account: 551234567890
    key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    compute:
        type: amazon
network:
    bind_host: _non_loopback:ipv4_


On this I get the exception:
{elasticsearch/0.16.2}: Initialization Failed ...
- NoClassSettingsException[Failed to load class setting
[discovery.type] with value [cloud]]
        ClassNotFoundException[cloud]

for the network.bind_host I tried eth0:ipv4 but this gives me host
notfound exception.

Any ideas? Can someone upload an elasticsearch.yml file able to do ec2
discovery for him with the 16.2 version?

On Jul 6, 2:40 pm, Ridvan Gyundogan <[hidden email]> wrote:

> Ah ok thanks I will try.
>
> On Wed, Jul 6, 2011 at 2:37 PM, Clinton Gormley <[hidden email]>wrote:
>
>
>
>
>
>
>
>
>
> > > I start only 1 node at the moment so sure it should be the master.
>
> > By master, Shay means the version of ElasticSearch that is currently
> > master on github, not a released version.
>
> > You need to download and compile it yourself:
>
> >http://www.elasticsearch.org/download/master/
>
> > clint
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

kimchy
Administrator
You need to set the discovery type to ec2: http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html. The blog post is outdated... .

And you don't have to use master to have discovery working on ec2. You can set network.host to whatever value you want, for example, the internal IP address. If you want teh same config across nodes, you can bind to the network interface name (http://www.elasticsearch.org/guide/reference/modules/network.html), for example: _en0:ipv4_.

On Wednesday, July 6, 2011 at 4:34 PM, Ridvan Gyundogan wrote:

Unfortunately using the trunk is not an option at the moment because
there are some maven dependencies to the 16.2 jar in our project.
We will upgrade to 0.17 once it is officially released.

Now I tried the "Zen" as described here:
http://www.elasticsearch.org/blog/2010/05/11/here-comes-the-cloud.html

my elasticsearch.yml on the slave looks like this:
cluster:
name: perftests

discovery:
type: cloud
zen:
ping__timeout: 30s
cloud:
account: 551234567890
key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
compute:
type: amazon
network:
bind__host: _non_loopback:ipv4_


On this I get the exception:
{elasticsearch/0.16.2}: Initialization Failed ...
- NoClassSettingsException[Failed to load class setting
[discovery.type] with value [cloud]]
ClassNotFoundException[cloud]

for the network.bind_host I tried eth0:ipv4 but this gives me host
notfound exception.

Any ideas? Can someone upload an elasticsearch.yml file able to do ec2
discovery for him with the 16.2 version?

On Jul 6, 2:40 pm, Ridvan Gyundogan <ridva...@gmail.com> wrote:
Ah ok thanks I will try.

On Wed, Jul 6, 2011 at 2:37 PM, Clinton Gormley <clin...@iannounce.co.uk>wrote:









I start only 1 node at the moment so sure it should be the master.

By master, Shay means the version of ElasticSearch that is currently
master on github, not a released version.

You need to download and compile it yourself:


clint

Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Ridvan Gyundogan
Thanks Shay.
Now it is bit better, at least I do not have an exception but still
the ec2 instances do not run as a cluster.
What I additionally did is the following. Enabled ping for the
security group with the ec2-authorise. Tried that the 2 machines can
ping each other.
Checked with telnet that the 2 machines can open each other's 9200 and
9300 ports. The 9301 - 9303 ports are open too but the other ports are
closed by default.
These are the 2 log files I have. First the master and next the one
which had to become a slave.At the bottom is the elasticsearch.yml
config file I use.
Any ideas what I need to change?

master:
[2011-07-06 18:14:42,458][INFO ][node                     ] [Jimmy
Woo] {elasticsearch/0.16.2}[2142]: initializing ...
[2011-07-06 18:14:42,468][INFO ][plugins                  ] [Jimmy
Woo] loaded [cloud-aws]
[2011-07-06 18:14:48,272][INFO ][node                     ] [Jimmy
Woo] {elasticsearch/0.16.2}[2142]: initialized
[2011-07-06 18:14:48,272][INFO ][node                     ] [Jimmy
Woo] {elasticsearch/0.16.2}[2142]: starting ...
[2011-07-06 18:14:48,414][INFO ][transport                ] [Jimmy
Woo] bound_address {inet[/10.224.50.50:9300]}, publish_address {inet[/
10.224.50.50:9300]}
[2011-07-06 18:14:52,797][INFO ][cluster.service          ] [Jimmy
Woo] new_master [Jimmy Woo][T_0Y3f_UQJmfuiqYYW7Ivg][inet[/
10.224.50.50:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-06 18:14:52,845][INFO ][discovery                ] [Jimmy
Woo] perftests/T_0Y3f_UQJmfuiqYYW7Ivg
[2011-07-06 18:14:52,893][INFO ][gateway                  ] [Jimmy
Woo] recovered [0] indices into cluster_state
[2011-07-06 18:14:52,894][INFO ][http                     ] [Jimmy
Woo] bound_address {inet[/10.224.50.50:9200]}, publish_address {inet[/
10.224.50.50:9200]}
[2011-07-06 18:14:52,895][INFO ][node                     ] [Jimmy
Woo] {elasticsearch/0.16.2}[2142]: started


slave:
[2011-07-06 18:18:07,733][INFO ][node                     ] [Machine
Teen] {elasticsearch/0.16.2}[1251]: initializing ...
[2011-07-06 18:18:07,741][INFO ][plugins                  ] [Machine
Teen] loaded [cloud-aws]
[2011-07-06 18:18:11,994][INFO ][node                     ] [Machine
Teen] {elasticsearch/0.16.2}[1251]: initialized
[2011-07-06 18:18:11,995][INFO ][node                     ] [Machine
Teen] {elasticsearch/0.16.2}[1251]: starting ...
[2011-07-06 18:18:12,105][INFO ][transport                ] [Machine
Teen] bound_address {inet[/10.234.227.72:9300]}, publish_address
{inet[/10.234.227.72:9300]}
[2011-07-06 18:18:16,242][INFO ][cluster.service          ] [Machine
Teen] new_master [Machine Teen][4vSbOGJqRx6q3Vi5HrJ_IA][inet[/
10.234.227.72:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-06 18:18:16,278][INFO ][discovery                ] [Machine
Teen] perftests/4vSbOGJqRx6q3Vi5HrJ_IA
[2011-07-06 18:18:16,305][INFO ][gateway                  ] [Machine
Teen] recovered [0] indices into cluster_state
[2011-07-06 18:18:16,312][INFO ][http                     ] [Machine
Teen] bound_address {inet[/10.234.227.72:9200]}, publish_address
{inet[/10.234.227.72:9200]}
[2011-07-06 18:18:16,313][INFO ][node                     ] [Machine
Teen] {elasticsearch/0.16.2}[1251]: started

elasticsearch.yml:
cluster:
  name: perftests

discovery:
    type: ec2
zen:
    ping_timeout: 30s

cloud:
    account: ABCDEFGIJKLAAAAAAAAAA  #here I use the "Access Key ID",
not the "Account Number"
    key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    compute:
        type: amazon


network:
    bind_host: _eth0:ipv4_



On Jul 6, 7:16 pm, Shay Banon <[hidden email]> wrote:

> You need to set the discovery type to ec2:http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html. The blog post is outdated... .
>
> And you don't have to use master to have discovery working on ec2. You can set network.host to whatever value you want, for example, the internal IP address. If you want teh same config across nodes, you can bind to the network interface name (http://www.elasticsearch.org/guide/reference/modules/network.html), for example: _en0:ipv4_.
>
>
>
>
>
>
>
> On Wednesday, July 6, 2011 at 4:34 PM, Ridvan Gyundogan wrote:
> > Unfortunately using the trunk is not an option at the moment because
> > there are some maven dependencies to the 16.2 jar in our project.
> >  We will upgrade to 0.17 once it is officially released.
>
> > Now I tried the "Zen" as described here:
> >http://www.elasticsearch.org/blog/2010/05/11/here-comes-the-cloud.html
>
> > my elasticsearch.yml on the slave looks like this:
> > cluster:
> >  name: perftests
>
> > discovery:
> >  type: cloud
> >  zen:
> >  ping_timeout: 30s
> > cloud:
> >  account: 551234567890
> >  key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >  compute:
> >  type: amazon
> > network:
> >  bind_host: _non_loopback:ipv4_
>
> > On this I get the exception:
> > {elasticsearch/0.16.2}: Initialization Failed ...
> > - NoClassSettingsException[Failed to load class setting
> > [discovery.type] with value [cloud]]
> >  ClassNotFoundException[cloud]
>
> > for the network.bind_host I tried eth0:ipv4 but this gives me host
> > notfound exception.
>
> > Any ideas? Can someone upload an elasticsearch.yml file able to do ec2
> > discovery for him with the 16.2 version?
>
> > On Jul 6, 2:40 pm, Ridvan Gyundogan <[hidden email] (http://gmail.com)> wrote:
> > > Ah ok thanks I will try.
>
> > > On Wed, Jul 6, 2011 at 2:37 PM, Clinton Gormley <[hidden email] (http://iannounce.co.uk)>wrote:
>
> > > > > I start only 1 node at the moment so sure it should be the master.
>
> > > > By master, Shay means the version of ElasticSearch that is currently
> > > > master on github, not a released version.
>
> > > > You need to download and compile it yourself:
>
> > > >http://www.elasticsearch.org/download/master/
>
> > > > clint
Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

kimchy
Administrator
Can you set logging for discovery to TRACE in the logging file and gist it?

On Wednesday, July 6, 2011 at 9:35 PM, Ridvan Gyundogan wrote:

Thanks Shay.
Now it is bit better, at least I do not have an exception but still
the ec2 instances do not run as a cluster.
What I additionally did is the following. Enabled ping for the
security group with the ec2-authorise. Tried that the 2 machines can
ping each other.
Checked with telnet that the 2 machines can open each other's 9200 and
9300 ports. The 9301 - 9303 ports are open too but the other ports are
closed by default.
These are the 2 log files I have. First the master and next the one
which had to become a slave.At the bottom is the elasticsearch.yml
config file I use.
Any ideas what I need to change?

master:
[2011-07-06 18:14:42,458][INFO ][node ] [Jimmy
Woo] {elasticsearch/0.16.2}[2142]: initializing ...
[2011-07-06 18:14:42,468][INFO ][plugins ] [Jimmy
Woo] loaded [cloud-aws]
[2011-07-06 18:14:48,272][INFO ][node ] [Jimmy
Woo] {elasticsearch/0.16.2}[2142]: initialized
[2011-07-06 18:14:48,272][INFO ][node ] [Jimmy
Woo] {elasticsearch/0.16.2}[2142]: starting ...
[2011-07-06 18:14:48,414][INFO ][transport ] [Jimmy
Woo] bound_address {inet[/10.224.50.50:9300]}, publish_address {inet[/
10.224.50.50:9300]}
[2011-07-06 18:14:52,797][INFO ][cluster.service ] [Jimmy
Woo] new_master [Jimmy Woo][T_0Y3f_UQJmfuiqYYW7Ivg][inet[/
10.224.50.50:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-06 18:14:52,845][INFO ][discovery ] [Jimmy
Woo] perftests/T_0Y3f_UQJmfuiqYYW7Ivg
[2011-07-06 18:14:52,893][INFO ][gateway ] [Jimmy
Woo] recovered [0] indices into cluster_state
[2011-07-06 18:14:52,894][INFO ][http ]] [Jimmy
Woo] bound_address {inet[/10.224.50.50:9200]}, publish_address {inet[/
10.224.50.50:9200]}
[2011-07-06 18:14:52,895][INFO ][node ]] [Jimmy
Woo] {elasticsearch/0.16.2}[2142]: started


slave:
[2011-07-06 18:18:07,733][INFO ][node ]] [Machine
Teen] {elasticsearch/0.16.2}[1251]: initializing ...
[2011-07-06 18:18:07,741][INFO ][plugins ] [Machine
Teen] loaded [cloud-aws]
[2011-07-06 18:18:11,994][INFO ][node ]] [Machine
Teen] {elasticsearch/0.16.2}[1251]: initialized
[2011-07-06 18:18:11,995][INFO ][node ]] [Machine
Teen] {elasticsearch/0.16.2}[1251]: starting ...
[2011-07-06 18:18:12,105][INFO ][transport ]] [Machine
Teen] bound_address {inet[/10.234.227.72:9300]}, publish_address
{inet[/10.234.227.72:9300]}
[2011-07-06 18:18:16,242][INFO ][cluster.service ] [Machine
Teen] new_master [Machine Teen][4vSbOGJqRx6q3Vi5HrJ_IA][inet[/
10.234.227.72:9300]], reason: zen-disco-join (elected_as_master)
[2011-07-06 18:18:16,278][INFO ][discovery ] [Machine
Teen] perftests/4vSbOGJqRx6q3Vi5HrJ_IA
[2011-07-06 18:18:16,305][INFO ][gateway ]] [Machine
Teen] recovered [0] indices into cluster_state
[2011-07-06 18:18:16,312][INFO ][http ]] [Machine
Teen] bound_address {inet[/10.234.227.72:9200]}, publish_address
{inet[/10.234.227.72:9200]}
[2011-07-06 18:18:16,313][INFO ][node ]] [Machine
Teen] {elasticsearch/0.16.2}[1251]: started

elasticsearch.yml:
cluster:
name: perftests

discovery:
type: ec2
zen:
ping_timeout: 30s

cloud:
account: ABCDEFGIJKLAAAAAAAAAA #here I use the "Access Key ID",
not the "Account Number"
key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
compute:
type: amazon


network:
bind_host: _eth0:ipv4_



On Jul 6, 7:16 pm, Shay Banon <shay.ba...@elasticsearch.com> wrote:
You need to set the discovery type to ec2:http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html. The blog post is outdated... .

And you don't have to use master to have discovery working on ec2. You can set network.host to whatever value you want, for example, the internal IP address. If you want teh same config across nodes, you can bind to the network interface name (http://www.elasticsearch.org/guide/reference/modules/network.html), for example: _en0:ipv4_.







On Wednesday, July 6, 2011 at 4:34 PM, Ridvan Gyundogan wrote:
Unfortunately using the trunk is not an option at the moment because
there are some maven dependencies to the 16.2 jar in our project.
 We will upgrade to 0.17 once it is officially released.


my elasticsearch.yml on the slave looks like this:
cluster:
 name: perftests

discovery:
 type: cloud
 zen:
 ping_timeout: 30s
cloud:
 account: 551234567890
 key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 compute:
 type: amazon
network:
 bind_host: _non_loopback:ipv4_

On this I get the exception:
{elasticsearch/0.16.2}: Initialization Failed ...
- NoClassSettingsException[Failed to load class setting
[discovery.type] with value [cloud]]
 ClassNotFoundException[cloud]

for the network.bind_host I tried eth0:ipv4 but this gives me host
notfound exception.

Any ideas? Can someone upload an elasticsearch.yml file able to do ec2
discovery for him with the 16.2 version?

On Jul 6, 2:40 pm, Ridvan Gyundogan <[hidden email] (http://gmail.com)> wrote:
Ah ok thanks I will try.

On Wed, Jul 6, 2011 at 2:37 PM, Clinton Gormley <[hidden email] (http://iannounce.co.uk)>wrote:

I start only 1 node at the moment so sure it should be the master.

By master, Shay means the version of ElasticSearch that is currently
master on github, not a released version.

You need to download and compile it yourself:


clint

Reply | Threaded
Open this post in threaded view
|

Re: EC2 discovery issue

Ridvan Gyundogan
Shay,
here is the gist:
https://gist.github.com/1069376

On Jul 6, 10:35 pm, Shay Banon <[hidden email]> wrote:

> Can you set logging for discovery to TRACE in the logging file and gist it?
>
> On Wednesday, July 6, 2011 at 9:35 PM, Ridvan Gyundogan wrote:
> > Thanks Shay.
> > Now it is bit better, at least I do not have an exception but still
> > the ec2 instances do not run as a cluster.
> > What I additionally did is the following. Enabled ping for the
> > security group with the ec2-authorise. Tried that the 2 machines can
> > ping each other.
> > Checked with telnet that the 2 machines can open each other's 9200 and
> > 9300 ports. The 9301 - 9303 ports are open too but the other ports are
> > closed by default.
> > These are the 2 log files I have. First the master and next the one
> > which had to become a slave.At the bottom is the elasticsearch.yml
> > config file I use.
> > Any ideas what I need to change?
>
> > master:
> > [2011-07-06 18:14:42,458][INFO ][node ] [Jimmy
> > Woo] {elasticsearch/0.16.2}[2142]: initializing ...
> > [2011-07-06 18:14:42,468][INFO ][plugins ] [Jimmy
> > Woo] loaded [cloud-aws]
> > [2011-07-06 18:14:48,272][INFO ][node ] [Jimmy
> > Woo] {elasticsearch/0.16.2}[2142]: initialized
> > [2011-07-06 18:14:48,272][INFO ][node ] [Jimmy
> > Woo] {elasticsearch/0.16.2}[2142]: starting ...
> > [2011-07-06 18:14:48,414][INFO ][transport ] [Jimmy
> > Woo] bound_address {inet[/10.224.50.50:9300]}, publish_address {inet[/
> > 10.224.50.50:9300]}
> > [2011-07-06 18:14:52,797][INFO ][cluster.service ] [Jimmy
> > Woo] new_master [Jimmy Woo][T_0Y3f_UQJmfuiqYYW7Ivg][inet[/
> > 10.224.50.50:9300]], reason: zen-disco-join (elected_as_master)
> > [2011-07-06 18:14:52,845][INFO ][discovery ] [Jimmy
> > Woo] perftests/T_0Y3f_UQJmfuiqYYW7Ivg
> > [2011-07-06 18:14:52,893][INFO ][gateway ] [Jimmy
> > Woo] recovered [0] indices into cluster_state
> > [2011-07-06 18:14:52,894][INFO ][http ] [Jimmy
> > Woo] bound_address {inet[/10.224.50.50:9200]}, publish_address {inet[/
> > 10.224.50.50:9200]}
> > [2011-07-06 18:14:52,895][INFO ][node ] [Jimmy
> > Woo] {elasticsearch/0.16.2}[2142]: started
>
> > slave:
> > [2011-07-06 18:18:07,733][INFO ][node ] [Machine
> > Teen] {elasticsearch/0.16.2}[1251]: initializing ...
> > [2011-07-06 18:18:07,741][INFO ][plugins ] [Machine
> > Teen] loaded [cloud-aws]
> > [2011-07-06 18:18:11,994][INFO ][node ] [Machine
> > Teen] {elasticsearch/0.16.2}[1251]: initialized
> > [2011-07-06 18:18:11,995][INFO ][node ] [Machine
> > Teen] {elasticsearch/0.16.2}[1251]: starting ...
> > [2011-07-06 18:18:12,105][INFO ][transport ] [Machine
> > Teen] bound_address {inet[/10.234.227.72:9300]}, publish_address
> > {inet[/10.234.227.72:9300]}
> > [2011-07-06 18:18:16,242][INFO ][cluster.service ] [Machine
> > Teen] new_master [Machine Teen][4vSbOGJqRx6q3Vi5HrJ_IA][inet[/
> > 10.234.227.72:9300]], reason: zen-disco-join (elected_as_master)
> > [2011-07-06 18:18:16,278][INFO ][discovery ] [Machine
> > Teen] perftests/4vSbOGJqRx6q3Vi5HrJ_IA
> > [2011-07-06 18:18:16,305][INFO ][gateway ] [Machine
> > Teen] recovered [0] indices into cluster_state
> > [2011-07-06 18:18:16,312][INFO ][http ] [Machine
> > Teen] bound_address {inet[/10.234.227.72:9200]}, publish_address
> > {inet[/10.234.227.72:9200]}
> > [2011-07-06 18:18:16,313][INFO ][node ] [Machine
> > Teen] {elasticsearch/0.16.2}[1251]: started
>
> > elasticsearch.yml:
> > cluster:
> >  name: perftests
>
> > discovery:
> >  type: ec2
> > zen:
> >  ping_timeout: 30s
>
> > cloud:
> >  account: ABCDEFGIJKLAAAAAAAAAA #here I use the "Access Key ID",
> > not the "Account Number"
> >  key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >  compute:
> >  type: amazon
>
> > network:
> >  bind_host: _eth0:ipv4_
>
> > On Jul 6, 7:16 pm, Shay Banon <[hidden email] (http://elasticsearch.com)> wrote:
> > > You need to set the discovery type to ec2:http://www.elasticsearch.org/guide/reference/modules/discovery/ec2.html. The blog post is outdated... .
>
> > > And you don't have to use master to have discovery working on ec2. You can set network.host to whatever value you want, for example, the internal IP address. If you want teh same config across nodes, you can bind to the network interface name (http://www.elasticsearch.org/guide/reference/modules/network.html), for example: _en0:ipv4_.
>
> > > On Wednesday, July 6, 2011 at 4:34 PM, Ridvan Gyundogan wrote:
> > > > Unfortunately using the trunk is not an option at the moment because
> > > > there are some maven dependencies to the 16.2 jar in our project.
> > > > We will upgrade to 0.17 once it is officially released.
>
> > > > Now I tried the "Zen" as described here:
> > > >http://www.elasticsearch.org/blog/2010/05/11/here-comes-the-cloud.html
>
> > > > my elasticsearch.yml on the slave looks like this:
> > > > cluster:
> > > > name: perftests
>
> > > > discovery:
> > > > type: cloud
> > > > zen:
> > > > ping_timeout: 30s
> > > > cloud:
> > > > account: 551234567890
> > > > key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > > > compute:
> > > > type: amazon
> > > > network:
> > > > bind_host: _non_loopback:ipv4_
>
> > > > On this I get the exception:
> > > > {elasticsearch/0.16.2}: Initialization Failed ...
> > > > - NoClassSettingsException[Failed to load class setting
> > > > [discovery.type] with value [cloud]]
> > > > ClassNotFoundException[cloud]
>
> > > > for the network.bind_host I tried eth0:ipv4 but this gives me host
> > > > notfound exception.
>
> > > > Any ideas? Can someone upload an elasticsearch.yml file able to do ec2
> > > > discovery for him with the 16.2 version?
>
> > > > On Jul 6, 2:40 pm, Ridvan Gyundogan <[hidden email] (http://gmail.com)> wrote:
> > > > > Ah ok thanks I will try.
>
> > > > > On Wed, Jul 6, 2011 at 2:37 PM, Clinton Gormley <[hidden email] (http://iannounce.co.uk)>wrote:
>
> > > > > > > I start only 1 node at the moment so sure it should be the master.
>
> > > > > > By master, Shay means the version of ElasticSearch that is currently
> > > > > > master on github, not a released version.
>
> > > > > > You need to download and compile it yourself:
>
> > > > > >http://www.elasticsearch.org/download/master/
>
> > > > > > clint
12