gRPC

gRPC 3 INVALID_ARGUMENT vs 8 RESOURCE_EXHAUSTED

Both gRPC 3 (INVALID_ARGUMENT) and 8 (RESOURCE_EXHAUSTED) belong to the gRPC Status Codes category. 3 indicates that the client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system. Meanwhile, 8 means that some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.

説明

The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.

このコードが表示される場合

A request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.

解決方法

Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints.

説明

Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.

このコードが表示される場合

A rate limit was hit, a quota was exceeded, or the server ran out of memory/disk. Common with API rate limiting and resource quotas.

解決方法

Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.

主な違い

1.

gRPC 3: The client specified an invalid argument. This indicates arguments that are problematic regardless of the state of the system.

2.

gRPC 8: Some resource has been exhausted, perhaps a per-user quota, or the entire file system is out of space.

3.

You encounter 3 when a request field failed validation — for example, a negative page size, a malformed email, or a required field left empty.

4.

You encounter 8 when a rate limit was hit, a quota was exceeded, or the server ran out of memory/disk. Common with API rate limiting and resource quotas.

どちらをいつ使うか

For 3 (INVALID_ARGUMENT): Inspect the request payload and fix the invalid field. Check the API documentation for expected formats and constraints. For 8 (RESOURCE_EXHAUSTED): Implement exponential backoff and retry. If quota-related, request a quota increase or optimize your usage pattern to stay within limits.

詳しく見る