gRPC 3 INVALID_ARGUMENT vs 10 ABORTED
Both gRPC 3 (INVALID_ARGUMENT) and 10 (ABORTED) belong to the gRPC Status Codes category. 3 indicates that the client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system. Meanwhile, 10 means that the operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
説明
The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
このコードが表示される場合
A request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
解決方法
Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.
説明
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.
主な違い
gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.
gRPC 10: The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
You encounter 3 when a request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.
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.
どちらをいつ使うか
For 3 (INVALID_ARGUMENT): Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints. For 10 (ABORTED): Retry the entire read-modify-write sequence from the beginning. Implement proper optimistic concurrency control with version tokens or ETags.