gRPC 5 NOT_FOUND vs 8 RESOURCE_EXHAUSTED
Both gRPC 5 (NOT_FOUND) and 8 (RESOURCE_EXHAUSTED) 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, 8 means that some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
Mô tả
Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
Khi bạn thấy mã này
The resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
Cách khắc phục
Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client.
Mô tả
Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
Khi bạn thấy mã này
A rate limit was hit, a quota was exceeded, or the server ran out of memory/disk. Common with API rate limiting and resource quotas.
Cách khắc phục
Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.
Sự khác biệt chính
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 8: Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.
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 8 when a rate limit was hit, a quota was exceeded, or the server ran out of memory/disk. Common with API rate limiting and resource quotas.
Khi nào dùng cái nào
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 8 (RESOURCE_EXHAUSTED): Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.