Quantcast

EC2 discovery issues

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

EC2 discovery issues

Marc Lennox
Been trying for a while to get a simple 3 node configuration going on EC2 (1 master with no data, 2 slaves with data).  I have trace logging setup and can see that the nodes discover each other correctly and connect, but then immediately disconnect.  Looking at the master through the /head/ plugin I only see the master and no shards are allocated.

Using 0.20.5 with the aws cloud plugin.

Any ideas where to start?

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: EC2 discovery issues

Marc Lennox
Funny, after banging my head for 4 hours and finally posting to this group, I figured out the issue immediately after the post.

I had to open up port 9300 in the security group in EC2.

Problem solved.

On Tuesday, 26 February 2013 23:45:09 UTC-5, Marc Lennox wrote:
Been trying for a while to get a simple 3 node configuration going on EC2 (1 master with no data, 2 slaves with data).  I have trace logging setup and can see that the nodes discover each other correctly and connect, but then immediately disconnect.  Looking at the master through the /head/ plugin I only see the master and no shards are allocated.

Using 0.20.5 with the aws cloud plugin.

Any ideas where to start?

--
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 [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Loading...