gRPC 1 CANCELLED vs 2 UNKNOWN
Both gRPC 1 (CANCELLED) and 2 (UNKNOWN) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. Meanwhile, 2 means that an unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
الوصف
The operation was cancelled, typically by the caller.
متى تراه
The client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
كيفية الإصلاح
If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain.
الوصف
An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
متى تراه
The server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
كيفية الإصلاح
Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN.
الفروق الرئيسية
gRPC 1: The operation was cancelled, typically by the caller.
gRPC 2: An unknown error occurred. This may be returned when a server raises an exception that doesn't map to any known gRPC status code.
You encounter 1 when the client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.
You encounter 2 when the server threw an unhandled exception or returned an error that gRPC couldn't classify into a more specific status code.
متى تستخدم أيًا منهما
For 1 (CANCELLED): If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain. For 2 (UNKNOWN): Check the server logs for the underlying exception. Wrap server-side errors with explicit gRPC status codes instead of letting them bubble up as UNKNOWN.