gRPC 0 OK vs 13 INTERNAL
Both gRPC 0 (OK) and 13 (INTERNAL) belong to the gRPC Status Codes category. 0 indicates that the operation completed successfully. Not an error; returned on success. Meanwhile, 13 means that an internal error occurred. This means that some invariant expected by the underlying system has been broken.
説明
The operation completed successfully. Not an error; returned on success.
このコードが表示される場合
The RPC completed without any issues. This is the expected response for every successful gRPC call.
解決方法
No fix needed — this indicates everything worked correctly.
説明
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 0: The operation completed successfully. Not an error; returned on success.
gRPC 13: An internal error occurred. This means that some invariant expected by the underlying system has been broken.
You encounter 0 when the RPC completed without any issues. This is the expected response for every successful gRPC call.
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 0 (OK): No fix needed — this indicates everything worked correctly. 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.