gRPC 6 ALREADY_EXISTS vs 15 DATA_LOSS
Both gRPC 6 (ALREADY_EXISTS) and 15 (DATA_LOSS) 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, 15 means that unrecoverable data loss or corruption has occurred.
説明
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.
説明
Unrecoverable data loss or corruption has occurred.
このコードが表示される場合
Critical data was lost or corrupted — for example, a checksum mismatch during transmission or an unrecoverable storage failure on the server.
解決方法
Investigate the data integrity failure immediately. Restore from backups if available, and check for hardware failures or network corruption in the data path.
主な違い
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 15: Unrecoverable data loss or corruption has occurred.
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 15 when critical data was lost or corrupted — for example, a checksum mismatch during transmission or an unrecoverable storage failure on the server.
どちらをいつ使うか
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 15 (DATA_LOSS): Investigate the data integrity failure immediately. Restore from backups if available, and check for hardware failures or network corruption in the data path.