知识卡片
深层探针可能触发全体摘流
深层探针执行关键业务依赖,更接近真实路径,也会给依赖增加负担。当共享数据库故障时,所有副本可能一起报告不健康,负载均衡若全部摘除就可能扩大失效。应限制探测成本并区分本地故障与共同依赖问题;存活重启与是否接流量不能被一个笼统健康值包办。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Resilience · 查看原书依据
issues with dependencies will be felt by the entire fleet — and you have the potential for a cascading failure. If you’re using deep health checks, you should take advantage of strategies like circuit breaking (which we covered in “Circuit Breaking”) where you can, and your load balancer should “fail open” (which we’ll discuss in
参考来源
- 位置:《Cloud Native Go》第09章《Resilience》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch09.xhtml)
- 结论依据:深层探针执行关键业务依赖,更接近真实路径,也会给依赖增加负担。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。
- 原始内容:issues with dependencies will be felt by the entire fleet — and you have the potential for a cascading failure. If you’re using deep health checks, you should take advantage of strategies like circuit breaking (which we covered in “Circuit Breaking”) where you can, and your load balancer should “fail open” (which we’ll discuss in