gRPC 11 OUT_OF_RANGE vs 14 UNAVAILABLE
Both gRPC 11 (OUT_OF_RANGE) and 14 (UNAVAILABLE) belong to the gRPC Status Codes category. 11 indicates that the operation was attempted past the valid range. For example, seeking or reading past the end of a file. Meanwhile, 14 means that the service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.
Descripción
The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
Cuándo lo verás
A pagination offset exceeded the available data, or an iterator moved past the end of a collection. Unlike INVALID_ARGUMENT, this depends on the current state of the data.
Cómo solucionarlo
Check the valid range before making the request. For pagination, use the total count or next-page token to avoid requesting beyond the last page.
Descripción
The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.
Cuándo lo verás
The server is overloaded, shutting down, or a network partition occurred. This is the most common code to retry on, as it's explicitly transient.
Cómo solucionarlo
Retry with exponential backoff. If persistent, check the server health, load balancer configuration, and network connectivity between client and server.
Diferencias clave
gRPC 11: The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
gRPC 14: The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.
You encounter 11 when a pagination offset exceeded the available data, or an iterator moved past the end of a collection. Unlike INVALID_ARGUMENT, this depends on the current state of the data.
You encounter 14 when the server is overloaded, shutting down, or a network partition occurred. This is the most common code to retry on, as it's explicitly transient.
Cuándo usar cada uno
For 11 (OUT_OF_RANGE): Check the valid range before making the request. For pagination, use the total count or next-page token to avoid requesting beyond the last page. For 14 (UNAVAILABLE): Retry with exponential backoff. If persistent, check the server health, load balancer configuration, and network connectivity between client and server.