gRPC 1 CANCELLED vs 8 RESOURCE_EXHAUSTED
Both gRPC 1 (CANCELLED) and 8 (RESOURCE_EXHAUSTED) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. Meanwhile, 8 means that some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
Descripción
The operation was cancelled, typically by the caller.
Cuándo lo verás
The client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
Cómo solucionarlo
If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain.
Descripción
Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
Cuándo lo verás
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ómo solucionarlo
Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.
Diferencias clave
gRPC 1: The operation was cancelled, typically by the caller.
gRPC 8: Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
You encounter 1 when the client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
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.
Cuándo usar cada uno
For 1 (CANCELLED): If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain. 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.