gRPC status 10: ABORTED
ABORTED is gRPC status code 10. The operation was aborted, typically by a concurrency conflict such as a failed transaction or sequencer check.
Updated
Usual causes
- A transaction was rolled back because of a conflicting write.
- An etag or version check failed: someone else changed the entity first.
What to check
- Whether two writers are updating the same entity at once.
- That the client re-reads before retrying, rather than sending the stale version again.
What it looks like
A typical error, as a Go client prints it: rpc error: code = Aborted desc = transaction aborted due to conflict, retry
Retry, and the HTTP equivalent
| ABORTED | |
|---|---|
| Code | 10 |
| Name | ABORTED |
| In istek's status bar | aborted |
| Retry | Yes, but at a higher level: re-read, re-apply the change, then send again. |
| HTTP status | 409 |
istek names the status of every call it makes, aborted included, and explains transport failures in plain words. See istek.