gRPC 2 UNKNOWN vs 14 UNAVAILABLE
Both gRPC 2 (UNKNOWN) and 14 (UNAVAILABLE) belong to the gRPC Status Codes category. 2 indicates that an unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code. Meanwhile, 14 means that the service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.
Beschreibung
An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
Wann Sie es sehen
The server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
Wie man es behebt
Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN.
Beschreibung
The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.
Wann Sie es sehen
The server is overloaded, shutting down, or a network partition occurred. This is the most common code to retry on, as it's explicitly transient.
Wie man es behebt
Retry with exponential backoff. If persistent, check the server health, load balancer configuration, and network connectivity between client and server.
Wesentliche Unterschiede
gRPC 2: An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
gRPC 14: The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.
You encounter 2 when the server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
You encounter 14 when the server is overloaded, shutting down, or a network partition occurred. This is the most common code to retry on, as it's explicitly transient.
Wann welchen verwenden
For 2 (UNKNOWN): Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN. For 14 (UNAVAILABLE): Retry with exponential backoff. If persistent, check the server health, load balancer configuration, and network connectivity between client and server.