gRPC 5 NOT_FOUND vs 15 DATA_LOSS
Both gRPC 5 (NOT_FOUND) and 15 (DATA_LOSS) 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, 15 means that unrecoverable data loss or corruption has occurred.
الوصف
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.
الوصف
Unrecoverable data loss or corruption has occurred.
متى تراه
Critical data was lost or corrupted — for example, a checksum mismatch during transmission or an unrecoverable storage failure on the server.
كيفية الإصلاح
Investigate the data integrity failure immediately. Restore from backups if available, and check for hardware failures or network corruption in the data path.
الفروق الرئيسية
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 15: Unrecoverable data loss or corruption has occurred.
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 15 when critical data was lost or corrupted — for example, a checksum mismatch during transmission or an unrecoverable storage failure on the server.
متى تستخدم أيًا منهما
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 15 (DATA_LOSS): Investigate the data integrity failure immediately. Restore from backups if available, and check for hardware failures or network corruption in the data path.