[英]SIGTERM signal arrives first to kuma and stops all active application connections immediately
we have applications that work with Kafka (MSK), we noticed that once pod is starting to shutdown (during autoscaling or deployment) the app container loses all active connections and the SIGTERM signal causes Kuma to close all connections immediately which cause data loss due to unfinished sessions (which doesn't get closed gracefully) on the app side and after that we receive connection errors to the kafka brokers, is anyone have an idea how to make Kuma wait some time once it gets the SIGTERM signal to let the sessions close gracefully?我们有与 Kafka (MSK) 配合使用的应用程序,我们注意到一旦 pod 开始关闭(在自动缩放或部署期间),应用程序容器将丢失所有活动连接并且 SIGTERM 信号导致 Kuma 立即关闭所有连接,这会导致数据丢失在应用程序端未完成的会话(没有正常关闭),之后我们收到到 kafka 代理的连接错误,有没有人知道如何让 Kuma 在收到 SIGTERM 信号后等待一段时间让会话关闭优雅地? or maybe a way to let the app know before the kuma about the shutsown?或者也许是一种让应用程序在 kuma 之前知道关闭的方法? or any other idea?或任何其他想法?
This is known issue getting fixed in the coming 1.7 release: https://github.com/kumahq/kuma/pull/4229这是在即将发布的 1.7 版本中得到修复的已知问题: https://github.com/kumahq/kuma/pull/4229
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.