blocks|key|1105241|text|通常，Kubernetes在没有重新启动现有的的情况下扩展了，所以这种情况在您的情况下是不会发生的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1105242|不过，撇开这一点不说，你的任何一款游戏机都不应该以导致信息丢失的方式关闭。这表明您是丢失了优雅关闭的代码。|1105243|使用Spring和K8s，您必须做两件事：|1105244|在Spring中引入一个关闭处理程序，它由K8s初始SIGTERM信号触发，并确保应用程序不接受新消息，但获得处理在运行中消息的时间。Spring为此提供了几种机制。|unordered-list-item|1105245|通过充分配置K8s，确保terminationGracePeriodSeconds为您的应用程序提供足够的时间来优雅地关闭。这是应用程序在K8s发送SIGKILL信号之前以有序的方式关闭自己的时间。|1105246|entityMap|0|LINK|mutability|MUTABLE|url|https://www.baeldung.com/spring-shutdown-callbacks|1|https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#podspec-v1-core^0|N|7|0|16|7|0|0|26|4|0|0|C|T|1|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|14|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|M|3|N|5|L|7|19|8|@]|D|@$9|1A|A|1B|1|1C]]|E|$]]|$1|O|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]|W|$5|R|S|T|E|$U|X]]]]

Normally, Kubernetes scales up without restarting the existing Pods, so kind of unusual that this does not happen in your case.
That aside though, none of your Pods should shut down in a way that results in loss of messages. This suggests that you are missing code for graceful shutdown.
With Spring Boot and K8s you will have to do two things:
<ul>
<li>Introduce a shutdown handler in Spring Boot that is triggered by K8s initial SIGTERM signal and makes sure the application does not accept new messages, but gets time to handle in-flight messages. Spring Boot provides <a href="https://www.baeldung.com/spring-shutdown-callbacks" rel="nofollow noreferrer">several mechanisms</a> for this.</li>
<li>Makes sure that K8s gives your application sufficient time for graceful shutdown by adequately configuring the <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#podspec-v1-core" rel="nofollow noreferrer">terminationGracePeriodSeconds</a>. This is the time your applications gets to shut itself down in an orderly manner before K8s sends the SIGKILL signal.</li>
</ul>

blocks|key|13648|text|正如David所建议的那样，我不仅修补了replicas的数量，而且还修补了template中的一个环境变量，从而重新创建了副本，以获取这个新变量。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|13649|Fritz的回答也是一个伟大的整体建议，一个优雅的关闭。|13650|entityMap^0|K|8|12|8|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

As David Maze suggested, I was not only patching the number of <code>replicas</code> but also patching an environment variable in the <code>template</code>, causing the replica to be recreated in order to pick that new variable up.
Fritz's answer is also a great overall suggestion for a graceful shutdown.

I have a Spring Boot application running in a Docker container managed by Kubernetes whose job is to pull data from a queue, process it, and write back to a queue. Initially, the Deployment for this application is created with 1 replica. However, at some point I need to scale that Deployment up in order to process messages from the queue faster. Ideally, I'd like to have that existing 1 replica start processing messages, and then the new replicas can come up and help out.
The problem I've discovered is that when scaling the Deployment programmatically, the existing 1 replica is destroyed, and this typically is occurring in the middle of it processing some data, resulting in the output of that processing being lost.
Example of what I'd like to see happen:
<ol>
<li>One replica processing message</li>
<li>Deployment gets scaled to 5 replicas</li>
<li>Four new replicas are spun up to help process messages leaving the existing.</li>
</ol>
Is this at all possible? Thanks!

Scale Kubernetes deployment without removing existing replicas

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个Spring应用程序运行在一个由Kubernetes管理的Docker容器中，该容器的任务是从队列中提取数据、处理数据并将其写回队列。最初，这个应用程序的部署是用一个副本创建的。但是，在某种程度上，我需要扩展部署，以便更快地处理来自队列的消息。理想情况下，我希望现有的1个副本开始处理消息，然后新副本可以出现并提...

问不移除现有副本的Kubernetes部署规模
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问不移除现有副本的Kubernetes部署规模EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问不移除现有副本的Kubernetes部署规模
EN