Jobs discarded even though attempts remained ?
还没有人认领这个 Issue。
评估
调研方向
The report names v0.31.0, Go 1.26, a service restart, and the job rescuer/cleaner log, but no source file or test. Start by reproducing the restart scenario and inspecting those logs and the affected jobs; done means identifying why max_attempts became 1 and documenting or testing the corrected behavior.
由索引模型根据 Issue 内容生成。
描述
I think I just encountered an issue where jobs were discarded and marked at "max_attempts=1" after a service restart.
I just upgraded to v0.31.0 (go 1.26).
I have a job type for which I know for a fact that we only ever enqueue them with the default value of max_attempts (so MaxAttempts=0 in the struct, meaning 25 attempts). I'm also fairly sure that nothing was modified manually.
All those jobs (252 succeeded, 78 discarded) where created at 2026-03-11 17:01:49.393302 +00:00 with a scheduled_at at the same time.
This happened just 2 minutes after a service restart, and about 8 second after an info log about the job rescuer / cleaner run.
I have no indication that my application code created those jobs, so I'm thinking some background job might have done something ?
I'm a bit out of ideas, but I thought I'd ask for an opinion here.
- 主要语言
- Go
- 星标
- 5.7k
- 派生
- 179
- 平均合并
- 2 天 19 小时
- 30 天内合并 PR
- 12
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
riverqueue/river 的其他 Issue
-
难度 5/5 一周以上 新手友好度 45/100
riverqueue/river#1358 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
riverqueue/river#1258 · 7 条评论 ·
-
难度 4/5 3-5 天 新手友好度 45/100
riverqueue/river#1225 · 14 条评论 ·
-
难度 4/5 3-5 天 新手友好度 52/100
riverqueue/river#1185 · 2 条评论 ·
-
难度 4/5 3-5 天 新手友好度 52/100
riverqueue/river#1183 · 2 个 reaction ·
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 90/100
-
enhancement
难度 2/5 1-3 小时 新手友好度 65/100
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100
santhosh-tekuri/jsonschema#276 ·