gRPC 1 CANCELLED vs 6 ALREADY_EXISTS
Both gRPC 1 (CANCELLED) and 6 (ALREADY_EXISTS) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. 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.
설명
The operation was cancelled, typically by the caller.
이 코드를 보게 되는 경우
The client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
해결 방법
If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain.
설명
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.
이 코드를 보게 되는 경우
A create operation failed because a resource with the same unique identifier or name already exists in the system.
해결 방법
Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating.
주요 차이점
gRPC 1: The operation was cancelled, typically by the caller.
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 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 6 when a create operation failed because a resource with the same unique identifier or name already exists in the system.
언제 어떤 것을 사용할지
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 6 (ALREADY_EXISTS): Use a different identifier, or switch to an upsert/update operation if overwriting is acceptable. Check for existing resources before creating.