← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 4545.f.1.a

健康检查先明确探测目的

理解等级:中级

书中区分三类探测:存活检查只证明端点可达,浅层检查验证本地资源,深层检查实际触及关键依赖。信息更多也意味着更高成本和共同失败风险。探针成功不是所有业务请求正确的证明;探针失败也可能来自网络或配置,使用它触发摘流或重启前必须明确语义。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Resilience · 查看原书依据

      Liveness checks do little more than return a “success” signal. They make no additional attempt to determine the status of the service, and say nothing about the service except that it’s listening and reachable. But, then again, sometimes this is enough. We’ll talk more about liveness checks in “Liveness Checks”. Shallow health checks go further

    参考来源

    - 位置:《Cloud Native Go》第09章《Resilience》(来源项目book-sources;源文件:extracted/Cloud Native Go (Matthew A. Titmus)/_epub-src/OEBPS/ch09.xhtml) - 结论依据:书中区分三类探测:存活检查只证明端点可达,浅层检查验证本地资源,深层检查实际触及关键依赖。原文相应定义、示例或限制为此结论提供依据;补充纠错与版本边界在正文就近标明。 - 原始内容:Liveness checks do little more than return a “success” signal. They make no additional attempt to determine the status of the service, and say nothing about the service except that it’s listening and reachable. But, then again, sometimes this is enough. We’ll talk more about liveness checks in “Liveness Checks”. Shallow health checks go further