gRPC 8 RESOURCE_EXHAUSTED vs 12 UNIMPLEMENTED
Both gRPC 8 (RESOURCE_EXHAUSTED) and 12 (UNIMPLEMENTED) belong to the gRPC Status Codes category. 8 indicates that some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space. Meanwhile, 12 means that the operation is not implemented or is not supported/enabled in this service.
Description
Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
When You See It
A rate limit was hit, a quota was exceeded, or the server ran out of memory/disk. Common with API rate limiting and resource quotas.
How to Fix
Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.
Description
The operation is not implemented or is not supported/enabled in this service.
When You See It
The client called an RPC method that the server does not implement. This often happens when the client uses a newer proto definition than the server supports.
How to Fix
Verify the server version supports the method you're calling. Update the server to implement the missing method, or use an alternative endpoint.
Key Differences
gRPC 8: Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
gRPC 12: The operation is not implemented or is not supported/enabled in this service.
You encounter 8 when a rate limit was hit, a quota was exceeded, or the server ran out of memory/disk. Common with API rate limiting and resource quotas.
You encounter 12 when the client called an RPC method that the server does not implement. This often happens when the client uses a newer proto definition than the server supports.
When to Use Which
For 8 (RESOURCE_EXHAUSTED): Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits. For 12 (UNIMPLEMENTED): Verify the server version supports the method you're calling. Update the server to implement the missing method, or use an alternative endpoint.