gRPC 2 UNKNOWN vs 8 RESOURCE_EXHAUSTED
Both gRPC 2 (UNKNOWN) and 8 (RESOURCE_EXHAUSTED) 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, 8 means that some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
Mô tả
An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
Khi bạn thấy mã này
The server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
Cách khắc phục
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.
Mô tả
Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
Khi bạn thấy mã này
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.
Cách khắc phục
Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.
Sự khác biệt chính
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 8: Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
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 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.
Khi nào dùng cái nào
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 8 (RESOURCE_EXHAUSTED): Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.