I am pretty sure you can open the ports for the sec group the elb belongs
to , regardless of the az. (Az, not region). Unless you r using network
acls.
Anyway, not really ES... pm me if u want to continue the AWS discussion :-)
On 16/10/2014 3:37 pm, Zoran Jeremic zoran.jere...@gmail.com wrote:
Hi Norberto,
Thank you so much for great advices.
As I'm starting tomorrow with real users, I'll keep for now the
configuration I have at the moment (all nodes have master=true, data=true).
I hope it will work.
For the zone availability, I had to go with everything in one zone. Main
reason
Inline below ...
On Sun, Oct 12, 2014 at 5:28 AM, Zoran Jeremic zoran.jere...@gmail.com
wrote:
Hi Norberto,
Thank you for your advices. This is really helpful, since I have never
used elasticsearch in the cluster before, and never had went live with a
number of users. My previous
Hi Norberto,
Thank you for your advices. This is really helpful, since I have never used
elasticsearch in the cluster before, and never had went live with a number
of users. My previous experience was on ES single node and very small
number of users, so I'm still concern how this will work.
Hi David,
Thank you for your quick response. That was great guess about the space
after :. It was really something that made a problem, so I'm now a step
forward. It seems that it's trying to establish the connection, but there
are a plenty of exceptions stating that Nework is unreachable. Why
Not sure but may be related to public/private IP.
May be debug logs will give you more insights?
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 10 oct. 2014 à 22:40, Zoran Jeremic zoran.jere...@gmail.com a écrit :
Hi David,
Thank you for your quick response. That
Hi David,
Thank you for your advices. It really helped me to solve the issue and make
it works.
At the end I had to leave these two:
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts:
[10.185.210.54[9300-9400],10.101.176.236[9300-9400]]
and to remove:
Zoran, good to hear it is working now.
It should work pretty well with ec2 auto discovery - unicast is a good
starting point but unless you are statically assigning them via cloud
formation (or manually?), it may not be worth the trouble (and it stops you
from dynamically scaling your cluster)
-
