Help debugging high load - connection error

Hi,

I need some help knowing where to look / which settings to turn on to help
me debug an issue. We've recently had a substantial increase in load and
are seeing getaddrinfo: Name or service not known from the elasticsearch
ruby gem.

For a bit of background, we have 3 elasticsearch servers in a cluster
behind an amazon load balancer. The servers themselves seem to be fine in
terms of CPU, Disk IO, etc. Cluster status is green. I can provide more
detail on servers / traffic if needed.

The logs at /var/log/elasticsearch don't indicate that anything is amiss.
Is that the right place to look? If the connection isn't even being made
then maybe the search servers don't know of anything going wrong?

I'm not sure how to debug if we're sending too much at the load balancer,
either, but I'd have thought those could handle a lot.

Cheers,
Nick

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/666f7344-4517-4401-8dc6-65c56071b9dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

That error would indicate a networking problem, specifically that it cannot
resolve DNS.

You could try adding a hosts entry to the ES node and see if that help.

On 18 February 2015 at 12:13, Nick Malcolm nick@revert.io wrote:

Hi,

I need some help knowing where to look / which settings to turn on to help
me debug an issue. We've recently had a substantial increase in load and
are seeing getaddrinfo: Name or service not known from the elasticsearch
ruby gem.

For a bit of background, we have 3 elasticsearch servers in a cluster
behind an amazon load balancer. The servers themselves seem to be fine in
terms of CPU, Disk IO, etc. Cluster status is green. I can provide more
detail on servers / traffic if needed.

The logs at /var/log/elasticsearch don't indicate that anything is amiss.
Is that the right place to look? If the connection isn't even being made
then maybe the search servers don't know of anything going wrong?

I'm not sure how to debug if we're sending too much at the load balancer,
either, but I'd have thought those could handle a lot.

Cheers,
Nick

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/666f7344-4517-4401-8dc6-65c56071b9dd%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/666f7344-4517-4401-8dc6-65c56071b9dd%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9EG0xpgAvSpjTU6hPes04EKda9k2%3DgqggHb1-QggB75w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.