gRPC

gRPC 1 CANCELLED vs 14 UNAVAILABLE

Both gRPC 1 (CANCELLED) and 14 (UNAVAILABLE) belong to the gRPC Status Codes category. 1 indicates that the operation was cancelled, typically by the caller. Meanwhile, 14 means that the service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.

Description

The operation was cancelled, typically by the caller.

When You See It

The client explicitly cancelled the RPC, or a deadline or context cancellation propagated to the server before it could finish processing.

How to Fix

If unexpected, check whether the client is setting too-short deadlines or if cancellation is being triggered inadvertently in your call chain.

Description

The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.

When You See It

The server is overloaded, shutting down, or a network partition occurred. This is the most common code to retry on, as it's explicitly transient.

How to Fix

Retry with exponential backoff. If persistent, check the server health, load balancer configuration, and network connectivity between client and server.

Key Differences

1.

gRPC 1: The operation was cancelled, typically by the caller.

2.

gRPC 14: The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff.

3.

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.

4.

You encounter 14 when the server is overloaded, shutting down, or a network partition occurred. This is the most common code to retry on, as it's explicitly transient.

When to Use Which

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 14 (UNAVAILABLE): Retry with exponential backoff. If persistent, check the server health, load balancer configuration, and network connectivity between client and server.

Learn More