grpc connection_error ai_generated true

UNAVAILABLE: all SubConns are in TransientFailure

ID: grpc/load-balancer-routing-error

Also available as: JSON · Markdown
78%Fix Rate
82%Confidence
3Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
1 active — — —

Root Cause

gRPC load balancer cannot find healthy backend.

generic

Workarounds

  1. 88% success Verify DNS/service discovery returns healthy backends
  2. 90% success Configure gRPC health checking: grpc.health.v1.Health

Dead Ends

Common approaches that don't work:

  1. Bypass load balancer and hardcode one server 80% fail

    No redundancy

  2. Remove health checking 85% fail

    Routes to dead backends