Month: August 2019

Kong: Failure to get a peer from the ring-balancer

Ever seen this error when calling kong:


HTTP/1.1 503 Service Temporarily Unavailable
Connection: keep-alive
Content-Length: 59
Content-Type: application/json; charset=utf-8
Date: Wed, 28 Aug 2019 08:08:01 GMT
Server: kong/0.14.1

{
    "message": "failure to get a peer from the ring-balancer"
}

What does it mean?

We it cannot access any of the upstreams or all of the upstreams are unhealthy.

It pretty much means Kong could connect to none of the backend services in the upstream pool.

Remember to ensure at least one upstream is healthy, otherwise unhealthy upstreams are ignored.

kong-upstream-unhealthy

Sources: