DEADLINE_EXCEEDED api runtime_error ai_generated partial

gRPC 错误：DEADLINE_EXCEEDED — 服务器过忙，无法在截止时间内响应

gRPC error: DEADLINE_EXCEEDED — server too busy to respond within deadline

ID: api/grpc-deadline-exceeded-server-busy

其他格式: JSON · Markdown 中文 · English
85%修复率
86%置信度
1证据数
2024-01-10首次发现

版本兼容性

版本状态引入弃用备注
gRPC 1.60+ active — — —
gRPC-Go 1.60+ active — — —
gRPC-Python 1.60+ active — — —

根因分析

gRPC 服务器由于高负载、资源争用或下游依赖缓慢，未能在客户端指定的截止时间内处理请求。

English

The gRPC server failed to process the request within the client-specified deadline due to high load, resource contention, or a slow downstream dependency.

generic

官方文档

https://grpc.io/docs/guides/error/

解决方案

  1. 实现客户端重试，使用指数退避和抖动。gRPC-Go 示例：`grpc.WithDefaultCallOptions(grpc.MaxRetryAttempts(3), grpc.WithBackoff(grpc.DefaultBackoffConfig))`。
  2. 通过添加更多实例或增加资源（CPU/内存）来扩展 gRPC 服务器。监控服务器指标（例如 `grpc_server_requests_in_flight`）。
  3. 降低请求复杂度或实现服务器端速率限制以防止过载。示例：在服务器配置中使用 `grpc.MaxConcurrentStreams`。

无效尝试

常见但无效的做法:

  1. 80% 失败

    If the server is overloaded, a longer deadline just delays the timeout; the request may still fail or degrade other requests.

  2. 90% 失败

    The server is still busy; immediate retries worsen load and likely fail again.

  3. 60% 失败

    The error is a server-side timeout, not a connection failure; network is likely fine.