Outbox prune and purge by handler read every failed row that the failed index cannot filter
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- csharp, postgresql, sqlite
- 领域
- database, performance
调研方向
Read the ix_cms_outbox_failed definition from PR #3406 and inspect OutboxPruneJob and OutboxDeadLetters to confirm the prune and purge queries. Measure both query plans with a large failed set; then either document the measured cost or propose an index change and obtain the required model slot. The issue gives no test or benchmark file, so first locate the query and database model tests.
由索引模型根据 Issue 内容生成。
描述
Problem
ix_cms_outbox_failed (PR #3406) is on cms_outbox (sequence DESC, id) filtered to status = 'failed'. It serves the dead-letter list exactly. Two other readers of failed rows also walk it, but filter on columns it does not hold, so they read every failed row to find the few they want:
- the prune of failed rows (
OutboxPruneJob):available_at < before AND attempts >= MaxAttempts; - the purge of a handler's dead letters (
OutboxDeadLetters, purge by handler):handler = ?.
With the 30-day retention the failed set stays bounded, but a burst of failures (a receiver down for days) makes each hourly prune batch, and each purge, read that whole set.
Proposal
Measure it with a realistic failed set first. If it matters, add the filtered columns to the index as included columns (PostgreSQL, SQL Server) or as trailing keys (SQLite). Or add a second filtered index on (handler, available_at). That is a model change, so it needs the model slot.
Acceptance
- The prune and purge-by-handler plans are checked with a large failed set, and either fixed or the cost is documented
- 主要语言
- C#
- 星标
- 567
- 派生
- 107
- 平均合并
- 1 小时 19 分钟
- 30 天内合并 PR
- 353
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
fluentcms/FluentCMS 的其他 Issue
-
area:localization plugin type:bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
area:storage type:bug
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 1 天内回复
-
area:testing type:bug
难度 3/5 1-2 天 新手友好度 72/100
维护者通常 1 天内回复
-
area:api area:publishing type:feature
难度 4/5 3-5 天 新手友好度 55/100
fluentcms/FluentCMS#3473 · 1 条评论 ·
维护者通常 1 天内回复
-
area:storage plugin type:bug
难度 5/5 一周以上 新手友好度 35/100
维护者通常 1 天内回复
查看 fluentcms/FluentCMS 的全部 Issue
相似的 Issue
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtime可能已有人在做 @Goldziher 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
priority:P2
难度 2/5 1-3 小时 新手友好度 82/100
-
bug sev-5 vm
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1-3 小时 新手友好度 85/100
-
area:jobads-cv bug FE mvp P3
难度 2/5 1-3 小时 新手友好度 77/100
klasolsson81/jobbliggaren#2271 ·
维护者通常 1 天内回复