gRPC 10 ABORTED vs 13 INTERNAL
Both gRPC 10 (ABORTED) and 13 (INTERNAL) 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, 13 means that an internal error occurred. This means that some invariant expected by the underlying system has been broken.
Описание
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.
Описание
An internal error occurred. This means that some invariant expected by the underlying system has been broken.
Когда вы это видите
A server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
Как исправить
Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.
Ключевые различия
gRPC 10: The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
gRPC 13: An internal error occurred. This means that some invariant expected by the underlying system has been broken.
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 13 when a server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
Когда что использовать
For 10 (ABORTED): Retry the entire read-modify-write sequence from the beginning. Implement proper optimistic concurrency control with version tokens or ETags. For 13 (INTERNAL): Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.