gRPC 2 UNKNOWN vs 6 ALREADY_EXISTS
Both gRPC 2 (UNKNOWN) and 6 (ALREADY_EXISTS) belong to the gRPC Status Codes category. 2 indicates that an unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code. Meanwhile, 6 means 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.
Descripción
An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
Cuándo lo verás
The server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
Cómo solucionarlo
Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN.
Descripción
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.
Cuándo lo verás
A create operation failed because a resource with the same unique identifier or name already exists in the system.
Cómo solucionarlo
Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating.
Diferencias clave
gRPC 2: An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
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.
You encounter 2 when the server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
You encounter 6 when a create operation failed because a resource with the same unique identifier or name already exists in the system.
Cuándo usar cada uno
For 2 (UNKNOWN): Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN. 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.