EC2 discovery finds some servers, but not all


(Marty) #1

I'm having trouble getting any 2 of my EC2 ES boxes to find any
other. I turned on more verbosity and see that ES has discovered all
100+ of my servers and listed them. It even tries to connect to port
9300 on a few, but not the right ones. Does ES give up after just a
few?


(Shay Banon) #2

Are all 100 servers part of the elasticsearch cluster? If not, then I
suggest using the ec2 discovery options to reduce (either based on tags or
security groups) the servers that will be pinged to include only the
elasticsearch servers.

There is a parameter called discovery.zen.ping.timeout which defaults to 3s
(3 seconds), you can increase it if you want it to be able to ping more
servers.

On Sun, Sep 11, 2011 at 6:28 AM, Marty marty@pinterest.com wrote:

I'm having trouble getting any 2 of my EC2 ES boxes to find any
other. I turned on more verbosity and see that ES has discovered all
100+ of my servers and listed them. It even tries to connect to port
9300 on a few, but not the right ones. Does ES give up after just a
few?


(system) #3