← 返回刚才阅读的位置

知识卡片

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

恢复节点先追平再接流量

理解等级:中级

节点恢复后需追赶停机期间的复制或事件日志,解决可能的分叉,再逐步恢复流量以预热缓存和连接池。恢复到进程启动不等于恢复业务能力;重放外部副作用还需去重。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Traffic Routing Strategies · 查看原书依据

      When a failed node recovers, it must reconcile data changes that occurred during its downtime. This requires mechanisms for replay/catch-up, as follows: Database replication: PostgreSQL uses logical replication to sync specific tables, while MySQL employs binary logs to replay write operations chronologically.

    参考来源

    - 位置:《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) - 结论依据:原文的机制或对比支持以下核心判断:节点恢复后需追赶停机期间的复制或事件日志,解决可能的分叉,再逐步恢复流量以预热缓存和连接池。 本卡将相邻说明中的适用限制保留为解释。 - 原始内容:When a failed node recovers, it must reconcile data changes that occurred during its downtime. This requires mechanisms for replay/catch-up, as follows: Database replication: PostgreSQL uses logical replication to sync specific tables, while MySQL employs binary logs to replay write operations chronologically.