gRPC 10 ABORTED vs 11 OUT_OF_RANGE
Both gRPC 10 (ABORTED) and 11 (OUT_OF_RANGE) 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, 11 means that the operation was attempted past the valid range. For example, seeking or reading past the end of a file.
描述
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.
描述
The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
何时出现
A pagination offset exceeded the available data, or an iterator moved past the end of a collection. Unlike INVALID_ARGUMENT, this depends on the current state of the data.
如何修复
Check the valid range before making the request. For pagination, use the total count or next-page token to avoid requesting beyond the last page.
主要区别
gRPC 10: The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
gRPC 11: The operation was attempted past the valid range. For example, seeking or reading past the end of a file.
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 11 when a pagination offset exceeded the available data, or an iterator moved past the end of a collection. Unlike INVALID_ARGUMENT, this depends on the current state of the data.
何时使用哪个
For 10 (ABORTED): Retry the entire read-modify-write sequence from the beginning. Implement proper optimistic concurrency control with version tokens or ETags. For 11 (OUT_OF_RANGE): Check the valid range before making the request. For pagination, use the total count or next-page token to avoid requesting beyond the last page.