"No server available to handle the request" thrown by AWS Elasticsearch Service

Asked May 14 '20 at 09:36

Active May 14 '20 at 13:34

Viewed 3,725 times

It doesn't happen regularly, but I was able to catch it in my debugger:

And then, because of that trailing comma, things further complicate. That error is not even well formatted JSON, which makes it throw DeserializationError, which is how it reaches my code. We can ignore this one, I just needed to bitch about it a little bit.

How do we find why is the "No server available to handle the request" happening? How to mitigate this?

If this is the expected behavior of an overloaded ES cluster, how do we properly handle this error specifically?

Here are the health metrics:

Here's context around the error:

edited May 14 '20 at 13:34

asked May 14 '20 at 09:36

Daniel Birowsky Popeski

8,752
12
60
125

How do the health metrics look like on AWS for that node? – Val May 14 '20 at 09:42
@Val added them at the bottom of the question. – Daniel Birowsky Popeski May 14 '20 at 09:55
health looks good. Are you hitting your nodes directly or are you going through a load balancer of some sort? – Val May 14 '20 at 09:59
@Val directly from Lambdas on AWS. – Daniel Birowsky Popeski May 14 '20 at 09:59
Anything useful in the headers? Care to paste them in your question? – Val May 14 '20 at 10:01
@Val Please clarify which headers : ) I'm using [this library](https://github.com/elastic/elasticsearch-js) to talk to Elasticsearch Service – Daniel Birowsky Popeski May 14 '20 at 10:02
Whatever is in the `headers` hash on your screenshot – Val May 14 '20 at 11:09
@Val Sorry, I still don't get it : / I can't find anything meaningful under the "headers" keyword on that page – Daniel Birowsky Popeski May 14 '20 at 11:18
1

On your screenshot, in the debug window, there's an object called `headers` can you show its content? – Val May 14 '20 at 11:19
Oh dear! I thought you were talking about the AWS console xD Let me catch that event again, and I'll let you know. – Daniel Birowsky Popeski May 14 '20 at 11:26
@Val finally caught it. I attached it at the bottom. Feel free to ask anything else. – Daniel Birowsky Popeski May 14 '20 at 13:35
Have you verified all these points (especially the first two)? https://aws.amazon.com/premiumsupport/knowledge-center/elasticsearch-http-503-errors/?nc1=h_ls – Val May 14 '20 at 13:40

"No server available to handle the request" thrown by AWS Elasticsearch Service

0 Answers0