gRPC 1 CANCELLED vs 13 INTERNAL
Both gRPC 1 (CANCELLED) and 13 (INTERNAL) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. Meanwhile, 13 means that an internal error occurred. This means that some invariant expected by the underlying system has been broken.
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
An internal error occurred. This means that some invariant expected by the underlying system has been broken.
Cuándo lo verás
A server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
Cómo solucionarlo
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.
Diferencias clave
gRPC 1: The operation was cancelled, typically by the caller.
gRPC 13: An internal error occurred. This means that some invariant expected by the underlying system has been broken.
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 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.
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 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.