gRPC 10 ABORTED vs 15 DATA_LOSS
Both gRPC 10 (ABORTED) and 15 (DATA_LOSS) belong to the gRPC Status Codes category. 10 indicates that the operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort. Meanwhile, 15 means that unrecoverable data loss or corruption has occurred.
説明
The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
このコードが表示される場合
A transaction or optimistic concurrency check failed — for example, a read-modify-write cycle detected a conflict with another concurrent operation.
解決方法
Retry the entire read-modify-write sequence from the beginning. Implement proper optimistic concurrency control with version tokens or ETags.
説明
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 10: The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
gRPC 15: Unrecoverable data loss or corruption has occurred.
You encounter 10 when a transaction or optimistic concurrency check failed — for example, a read-modify-write cycle detected a conflict with another concurrent operation.
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 10 (ABORTED): Retry the entire read-modify-write sequence from the beginning. Implement proper optimistic concurrency control with version tokens or ETags. 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.