gRPC 6 ALREADY_EXISTS vs 11 OUT_OF_RANGE
Both gRPC 6 (ALREADY_EXISTS) and 11 (OUT_OF_RANGE) belong to the gRPC Status Codes category. 6 indicates that the entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists. Meanwhile, 11 means that the operation was attempted past the valid range. For example, seeking or reading past the end of a file.
Descrição
The entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists.
Quando você o vê
A create operation failed because a resource with the same unique identifier or name already exists in the system.
Como corrigir
Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating.
Descrição
The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
Quando você o vê
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.
Como corrigir
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.
Diferenças principais
gRPC 6: The entity that a client attempted to create already exists. For example, a file or directory that the RPC was supposed to create already exists.
gRPC 11: The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
You encounter 6 when a create operation failed because a resource with the same unique identifier or name already exists in the system.
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.
Quando usar qual
For 6 (ALREADY_EXISTS): Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating. 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.