gRPC 5 NOT_FOUND vs 10 ABORTED
Both gRPC 5 (NOT_FOUND) and 10 (ABORTED) belong to the gRPC Status Codes category. 5 indicates that some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist. Meanwhile, 10 means that the operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
विवरण
Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
जब आप इसे देखें
The resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
कैसे ठीक करें
Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client.
विवरण
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 5: Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
gRPC 10: The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort.
You encounter 5 when the resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
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 5 (NOT_FOUND): Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client. For 10 (ABORTED): Retry the entire read-modify-write sequence from the beginning. Implement proper optimistic concurrency control with version tokens or ETags.