`GET /api/v1/sdk/ruleset` stops answering under sustained overload and does not recover after a pause

已关闭
  • 哪里不对？
#1,728 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

已经有一个关联 PR 被合并了。

  • #1754 来自 @amarkanday —— 已合并

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
api, backend, performance

调研方向

Start by locating the handler for GET /api/v1/sdk/ruleset and the in-process tests for that route. Read how the handler manages requests under load, then add a test that drives it past capacity and fails on release 0.42.0. Done when the test shows the route continues answering some requests during overload and recovers after load pauses.

由索引模型根据 Issue 内容生成。

描述

bug

What happens

Under sustained overload, GET /api/v1/sdk/ruleset stops answering altogether, and it is still not answering after the load
has paused for 12 to 17 seconds.

Seen in all three runs of the ruleset scenario in scale measurement run 41732112985 (release 0.42.0, GitHub-hosted runners,
two different CPU models). In each run, at the first step the API could not keep up with:

  • answered requests fell to zero for the rest of the step (after 6 to 30 seconds of normal answers);
  • the API's CPU use fell (from about 65-71% to 13-40% of a core) instead of staying saturated, and the database had no
    active connections serving it;
  • the proxy recorded every request in that stretch as closed by the client (499);
  • the next step started after a 12-17 s pause and answered nothing from its first second (0 of 2,268, 0 of 2,856 and 0 of
    3,598 requests).

What should happen

Past its capacity, the route may slow down or refuse some requests, but answered throughput should not collapse to zero, and
the route should answer normally again soon after the load drops.

Why it matters

Server-side SDKs in local-evaluation mode poll this route to refresh their rules. During a stall they keep serving their
last-known rules, as designed, but cannot pick up a change, so a flag change or a kill switch does not reach them until the
route recovers.

Notes

  • Priority: medium, before launch (D213: it touches use case #4, server-side local evaluation).
  • The measurement's report labelled these steps as database-bound ("serialised"). That label is wrong for this case and is
    being corrected in the scale harness as part of #1608. The run itself is discarded from the published evidence.
  • A fix needs an in-process test that drives this route past its capacity and fails on 0.42.0's code.
主要语言
Python
星标
0
派生
4
平均合并
6 小时 5 分钟
30 天内合并 PR
453

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

Controlvar/controlvar 的其他 Issue

查看 Controlvar/controlvar 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。