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.

Beschreibung

The operation was cancelled, typically by the caller.

Wann Sie es sehen

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

Wie man es behebt

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

Beschreibung

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

Wann Sie es sehen

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.

Wie man es behebt

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

Wesentliche Unterschiede

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.

Wann welchen verwenden

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.

Mehr erfahren