gRPC 8 RESOURCE_EXHAUSTED vs 13 INTERNAL
Both gRPC 8 (RESOURCE_EXHAUSTED) and 13 (INTERNAL) 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, 13 means that an internal error occurred. This means that some invariant expected by the underlying system has been broken.
Descrição
Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
Quando você o vê
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.
Como corrigir
Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.
Descrição
An internal error occurred. This means that some invariant expected by the underlying system has been broken.
Quando você o vê
A server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
Como corrigir
Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.
Diferenças principais
gRPC 8: Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
gRPC 13: An internal error occurred. This means that some invariant expected by the underlying system has been broken.
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 13 when a server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
Quando usar qual
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 13 (INTERNAL): Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.