知识卡片
超时重试遗留预留资源
邮寄标签系统在周日晚流量上升时扩容客户端,下游号码服务来不及处理,调用超时后重试又预留一个号码。最终成功请求将新号码置为used,先前请求的号码却永久留在reserved。问题是超时没有撤销实际资源占用,重试又不是同一逻辑操作的复用。原书未展开修复细节,不把猜想的回收算法当成已给方案。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Centralized Architecture Practices in a Decentralized World · 查看原书依据
It turned out to be the result of a “clever” thing we’d done: we built in an elastic scaling capability for our services so that we would have the right number of instances running when we needed them. What was happening was that, as we scaled all the services rapidly, the system would issue more
参考来源
- 位置:《Facilitating Software Architecture》第01章《Centralized Architecture Practices in a Decentralized World》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch01.html)
- 结论依据:原文给出扩容、超时、重新预留及缺失回收的具体链路;此为资源泄漏案例而非已发生重复扣款。
- 原始内容:It turned out to be the result of a “clever” thing we’d done: we built in an elastic scaling capability for our services so that we would have the right number of instances running when we needed them. What was happening was that, as we scaled all the services rapidly, the system would issue more