gRPC 0 OK vs 14 UNAVAILABLE
Both gRPC 0 (OK) and 14 (UNAVAILABLE) belong to the gRPC Status Codes category. 0 indicates that the operation completed successfully. Not an error; returned on success. 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.
Description
The operation completed successfully. Not an error; returned on success.
When You See It
The RPC completed without any issues. This is the expected response for every successful gRPC call.
How to Fix
No fix needed — this indicates everything worked correctly.
Description
The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.
When You See It
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.
How to Fix
Retry with exponential backoff. If persistent, check the server health, load balancer configuration, and network connectivity between client and server.
Key Differences
gRPC 0: The operation completed successfully. Not an error; returned on success.
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 0 when the RPC completed without any issues. This is the expected response for every successful gRPC call.
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.
When to Use Which
For 0 (OK): No fix needed — this indicates everything worked correctly. For 14 (UNAVAILABLE): Retry with exponential backoff. If persistent, check the server health, load balancer configuration, and network connectivity between client and server.