← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 2313.e.5.f.10.a.3.c.3.a

渐进恢复避免二次故障

理解等级:中级

给恢复节点逐步增加权重,观察错误、延迟和资源指标,异常时停止或回退。这样让缓存和连接逐渐预热,避免瞬间全量流量把尚未稳定的节点再次压垮。示意比例与时间须结合容量验证。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Traffic Routing Strategies · 查看原书依据

      Flooding a recovered node with 100% traffic immediately risks overloading it. Instead we can use the following techniques: Weighted routing: AWS Route 53 can shift traffic incrementally, for example, 5% → 20% → 50% → 100% over 30 minutes.

    参考来源

    - 位置:《Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…》第07章《Traffic Routing Strategies》(来源项目book-sources;源文件:extracted/Building Distributed Systems Designing scalable architectures with microservices, event-driven patterns, and robust deployment…/_epub-src/OPS/ch07.xhtml) - 结论依据:原文的机制或对比支持以下核心判断:给恢复节点逐步增加权重,观察错误、延迟和资源指标,异常时停止或回退。 本卡将相邻说明中的适用限制保留为解释。 - 原始内容:Flooding a recovered node with 100% traffic immediately risks overloading it. Instead we can use the following techniques: Weighted routing: AWS Route 53 can shift traffic incrementally, for example, 5% → 20% → 50% → 100% over 30 minutes.