gRPC 5 NOT_FOUND vs 14 UNAVAILABLE
Both gRPC 5 (NOT_FOUND) and 14 (UNAVAILABLE) 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, 14 means that the service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.
Açıklama
Some requested entity was not found. For example, a file or directory that the RPC was supposed to operate on does not exist.
Gördüğünüzde
The resource referenced in the request doesn't exist — such as looking up a user by ID that has been deleted or never created.
Nasıl Düzeltilir
Verify the resource identifier is correct. Ensure the resource was created before accessing it, or handle the not-found case gracefully in your client.
Açıklama
The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.
Gördüğünüzde
The server is overloaded, shutting down, or a network partition occurred. This is the most common code to retry on, as it's explicitly transient.
Nasıl Düzeltilir
Retry with exponential backoff. If persistent, check the server health, load balancer configuration, and network connectivity between client and server.
Temel Farklar
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 14: The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.
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 14 when the server is overloaded, shutting down, or a network partition occurred. This is the most common code to retry on, as it's explicitly transient.
Hangisini Ne Zaman Kullanmalı
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 14 (UNAVAILABLE): Retry with exponential backoff. If persistent, check the server health, load balancer configuration, and network connectivity between client and server.