Indicates that a request failed because no servers were available. The
Finagle client's internal load balancer was empty. This typically occurs
under one of the following conditions:
- The cluster is actually down. No servers are available.
- A service discovery failure. This can be due to a number of causes, such as
the client being constructed with an invalid cluster destination name [1]
or a failure in the service discovery system (e.g. DNS, ZooKeeper).
A good way to diagnose NoBrokersAvailableExceptions is to reach out to the
owners of the service to which the client is attempting to connect and verify
that the service is operational. If so, then investigate the service
discovery mechanism that the client is using (e.g. the
com.twitter.finagle.Resolver that is it configured to use and the system
backing it).
Indicates that a request failed because no servers were available. The Finagle client's internal load balancer was empty. This typically occurs under one of the following conditions:
- The cluster is actually down. No servers are available. - A service discovery failure. This can be due to a number of causes, such as the client being constructed with an invalid cluster destination name [1] or a failure in the service discovery system (e.g. DNS, ZooKeeper).
A good way to diagnose NoBrokersAvailableExceptions is to reach out to the owners of the service to which the client is attempting to connect and verify that the service is operational. If so, then investigate the service discovery mechanism that the client is using (e.g. the com.twitter.finagle.Resolver that is it configured to use and the system backing it).
[1] http://twitter.github.io/finagle/guide/Names.html