gRPC 1 CANCELLED vs 4 DEADLINE_EXCEEDED
Both gRPC 1 (CANCELLED) and 4 (DEADLINE_EXCEEDED) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. Meanwhile, 4 means that the deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully.
描述
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.
描述
The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully.
何时出现
The RPC took longer than the configured deadline allows. Common in slow network conditions, overloaded servers, or when the deadline is set too aggressively.
如何修复
Increase the client deadline, optimize the server-side processing, or add server-side caching. If the operation might have succeeded, check idempotency before retrying.
主要区别
gRPC 1: The operation was cancelled, typically by the caller.
gRPC 4: The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully.
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 4 when the RPC took longer than the configured deadline allows. Common in slow network conditions, overloaded servers, or when the deadline is set too aggressively.
何时使用哪个
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 4 (DEADLINE_EXCEEDED): Increase the client deadline, optimize the server-side processing, or add server-side caching. If the operation might have succeeded, check idempotency before retrying.