知识卡片
全停部署的状态边界
全停更新需先验证流、权限和模式,再停止旧实例,按明确方案处理状态、内部流和offset,启动后观察lag、日志与接口。保留旧状态和独立服务可缩短回退,但清理后只回滚代码不能自动找回数据。重放的I/O和输出会影响下游,因此部署完成标准应含恢复到可接受服务水平。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Deploying Event-Driven Microservices · 查看原书依据
Stop instances and perform any clean-up before deploying. Stop the microservice instances. Perform any necessary state store resets and/or consumer group resets, and delete any internal streams. If rebuilding state in the case deployment failure is expensive, you may instead want to leave your state, consumer group, and internal topics alone, and instead deploy as a new service. This will enable you to roll back quickly in the case of
参考来源
- 位置:《Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)》第16章《Deploying Event-Driven Microservices》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Event-Driven Microservices Leveraging Organizational Data at Scale (Adam Bellemare)/_epub-src/OEBPS/ch16.xhtml;规范化段落起句:Stop instances and perform any clean-up)
- 结论依据:原文对该对象的定义、运行说明或对比支持以下归纳:全停更新需先验证流、权限和模式,再停止旧实例,按明确方案处理状态、内部流和offset,启动后观察lag、日志与接口。本卡同时保留其适用条件与失败边界。
- 原始内容:Stop instances and perform any clean-up before deploying. Stop the microservice instances. Perform any necessary state store resets and/or consumer group resets, and delete any internal streams. If rebuilding state in the case deployment failure is expensive, you may instead want to leave your state, consumer group, and internal topics alone, and instead deploy as a new service. This will enable you to roll back quickly in the case of