Release, recovery and deferral of outbox batches still cost a write per row
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 52/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- csharp
- 领域
- backend, databases, performance
调研方向
Start by reading OutboxDrainer.ReleaseAsync and the claim logic it uses for leased rows; then trace how each lane reads PluginState and builds the deferred-id exclusion list. Check the existing outbox tests before changing behavior. Done means each proposal item is fixed or explicitly declined in the PR, with tests covering every fix.
由索引模型根据 Issue 内容生成。
描述
Problem
These are left over from the review of PR #3404 (outbox lanes per owner). None of them loses an event; they cost writes, time or log noise.
- Release on shutdown, row by row and without a token. A stopping host releases each unclaimed row of a batch with its own conditional
UPDATE(OutboxDrainer.ReleaseAsync), and the update takes no cancellation token. A large batch can therefore hold shutdown forBatchSizewrites. - Recovery after a failed release is row by row. A release that fails leaves the row leased with its claim attempt counted. Once the lease lapses, the row is claimed alone because it still names an owner. A whole failed batch is then recovered one claim per row.
- Deferrals cost a write each while plugin state is down. When
PluginStatecannot be read, every row of a batch is released and deferred with one write each. Each later drain then repeats the read of the plugin state for every lane. - Deferrals are bounded by time only. A deferred row is skipped for
MissingHandlerDelay, and the set of deferred ids is not capped. Their ids also go into every claim as aNOT INparameter list. A long thread-pool starvation can make that list long.
Proposal
- Release the rest of a batch with one
UPDATE ... WHERE id IN (...), bounded by a short timeout. - After a lapsed lease, claim alone only the first row that names a dead owner, not each of them.
- Read plugin state once per lane pass, and on failure release the batch in one write.
- Cap the deferred set, for example at
BatchSize, and leave the oldest out of theNOT INlist.
Acceptance
- Each item fixed or explicitly declined in its PR, with tests for those fixed
- 主要语言
- 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
-
[Bug]: Threading.Analyzers 0.7.79 does not load on the .NET 10 SDK (CS9057), CHT rules silently off未关闭bug regression threading
难度 2/5 1-3 小时 新手友好度 74/100
CryptoHives/Foundation#362 ·
维护者通常 1 天内回复
-
bug need-triage
难度 2/5 1-3 小时 新手友好度 65/100
Fervent-Tempo/AF-Media-Bar#321 ·
-
a-corriger documentation
难度 1/5 1 小时以内 新手友好度 87/100
christian-raj/S-Aloha#345 ·
-
bug 要トリアージ
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复
-
worldInstancedOccluderNode reads its appendix count as one byte, but it is a VLQ可能已有人在做 @spuddeh 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 78/100
维护者通常 1 天内回复