gRPC 4 DEADLINE_EXCEEDED vs 15 DATA_LOSS
Both gRPC 4 (DEADLINE_EXCEEDED) and 15 (DATA_LOSS) belong to the gRPC Status Codes category. 4 indicates that the deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully. Meanwhile, 15 means that unrecoverable data loss or corruption has occurred.
説明
The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully.
このコードが表示される場合
The RPC took longer than the configured deadline allows. Common in slow network conditions, overloaded servers, or when the deadline is set too aggressively.
解決方法
Increase the client deadline, optimize the server-side processing, or add server-side caching. If the operation might have succeeded, check idempotency before retrying.
説明
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 4: The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully.
gRPC 15: Unrecoverable data loss or corruption has occurred.
You encounter 4 when the RPC took longer than the configured deadline allows. Common in slow network conditions, overloaded servers, or when the deadline is set too aggressively.
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 4 (DEADLINE_EXCEEDED): Increase the client deadline, optimize the server-side processing, or add server-side caching. If the operation might have succeeded, check idempotency before retrying. 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.