gRPC 8 RESOURCE_EXHAUSTED vs 16 UNAUTHENTICATED
Both gRPC 8 (RESOURCE_EXHAUSTED) and 16 (UNAUTHENTICATED) 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, 16 means that the request does not have valid authentication credentials for the operation.
描述
Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
何时出现
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.
如何修复
Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.
描述
The request does not have valid authentication credentials for the operation.
何时出现
No credentials were provided, or the provided token/certificate is expired or invalid. Different from PERMISSION_DENIED (code 7), which means authenticated but not authorized.
如何修复
Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).
主要区别
gRPC 8: Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
gRPC 16: The request does not have valid authentication credentials for the operation.
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 16 when no credentials were provided, or the provided token/certificate is expired or invalid. Different from PERMISSION_DENIED (code 7), which means authenticated but not authorized.
何时使用哪个
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 16 (UNAUTHENTICATED): Provide valid authentication credentials (e.g., refresh the OAuth token, regenerate the API key, or renew the client certificate).