gRPC 2 UNKNOWN vs 13 INTERNAL
Both gRPC 2 (UNKNOWN) and 13 (INTERNAL) belong to the gRPC Status Codes category. 2 indicates 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. Meanwhile, 13 means that an internal error occurred. This means that some invariant expected by the underlying system has been broken.
描述
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.
描述
An internal error occurred. This means that some invariant expected by the underlying system has been broken.
何时出现
A server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
如何修复
Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.
主要区别
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.
gRPC 13: An internal error occurred. This means that some invariant expected by the underlying system has been broken.
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.
You encounter 13 when a server-side bug, a corrupted internal state, or an unexpected failure in a dependency. This is the gRPC equivalent of HTTP 500.
何时使用哪个
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. For 13 (INTERNAL): Check the server error logs and traces for the root cause. This typically indicates a bug that needs to be fixed in the server code.