Kafka Streams 2.3离线迁移至2.6后应用无法稳定运行问题咨询
Kafka Streams 从v2.3离线迁移到v2.6的运行异常说明
核心诉求
现有Kafka Streams应用从v2.3版本离线升级到v2.6版本的过程中,是否需要调整配置项,才能匹配升级前的运行效果?
基础环境与问题背景
- 集群环境:Kafka Broker已部署2.6版本服务端,应用仅升级Kafka Streams依赖库版本从v2.3到v2.6,未修改任何业务逻辑
- 部署架构:3个Pod组成消费组,消费包含30个分区的业务Topic,消费后通过
mapValues()算子做消息处理,单条消息处理耗时10-500ms,属于正常业务耗时范围 - 预期目标:升级后运行行为与v2.3版本完全一致
- 实际异常表现:
- 初期调整以下参数未解决问题:
session.timeout.ms=30000 max.poll.records=20 num.stream.threads=10 - 应用运行10-15分钟后,仅能实现数秒的短暂稳定,此时消费组仅存在5-6个成员,随即再次触发重平衡
- 初期未启用Kafka Streams静态成员资格机制,初期目标为不依赖该机制实现稳定运行
- 升级前v2.3版本可稳定支撑800条/秒的处理吞吐量,升级后因持续触发重平衡,吞吐量仅能达到50条/秒
- 初期调整以下参数未解决问题:
应用初始消费端配置明细
allow.auto.create.topics = true auto.commit.interval.ms = 5000 auto.offset.reset = latest bootstrap.servers = [pp5-kafka-acc-headless.pp5-acc:9092] check.crcs = true client.dns.lookup = default client.id = HeadEndPushServiceLowNetinium-211cbe23-50b2-4942-95f1-b93567d145c2-StreamThread-8-consumer client.rack = connections.max.idle.ms = 540000 default.api.timeout.ms = 60000 enable.auto.commit = false exclude.internal.topics = true fetch.max.bytes = 200000 fetch.max.wait.ms = 500 fetch.min.bytes = 1 group.id = HeadEndPushServiceLowNetinium group.instance.id = null heartbeat.interval.ms = 3000 interceptor.classes = [] internal.leave.group.on.close = false isolation.level = read_uncommitted key.deserializer = class org.apache.kafka.common.serialization.ByteArrayDeserializer max.partition.fetch.bytes = 1048576 max.poll.interval.ms = 300000 max.poll.records = 5 metadata.max.age.ms = 300000 metric.reporters = [] metrics.num.samples = 2 metrics.recording.level = INFO metrics.sample.window.ms = 30000 partition.assignment.strategy = [org.apache.kafka.streams.processor.internals.StreamsPartitionAssignor] receive.buffer.bytes = 65536 reconnect.backoff.max.ms = 1000 reconnect.backoff.ms = 50 request.timeout.ms = 30000 retry.backoff.ms = 100 sasl.client.callback.handler.class = null sasl.jaas.config = null sasl.kerberos.kinit.cmd = /usr/bin/kinit sasl.kerberos.min.time.before.relogin = 60000 sasl.kerberos.service.name = null sasl.kerberos.ticket.renew.jitter = 0.05 sasl.kerberos.ticket.renew.window.factor = 0.8 sasl.login.callback.handler.class = null sasl.login.class = null sasl.login.refresh.buffer.seconds = 300 sasl.login.refresh.min.period.seconds = 60 sasl.login.refresh.window.factor = 0.8 sasl.login.refresh.window.jitter = 0.05 sasl.mechanism = GSSAPI security.protocol = PLAINTEXT send.buffer.bytes = 131072 session.timeout.ms = 30000 ssl.cipher.suites = null ssl.enabled.protocols = [TLSv1.2, TLSv1.1, TLSv1] ssl.endpoint.identification.algorithm = https ssl.key.password = null ssl.keymanager.algorithm = SunX509 ssl.keystore.location = null ssl.keystore.password = null ssl.keystore.type = JKS ssl.protocol = TLS ssl.provider = null ssl.secure.random.implementation = null ssl.trustmanager.algorithm = PKIX ssl.truststore.location = null ssl.truststore.password = null ssl.truststore.type = JKS value.deserializer = class org.apache.kafka.common.serialization.ByteArrayDeserializer
调参后的初步优化效果
- 调整配置:将
session.timeout.ms设置为180000(3分钟),为每个Pod配置值为Pod名称的group.instance.id - 优化后表现:在总30个Stream线程的配置下稳定性明显提升,删除Pod后应用恢复稳定的时长在2分钟到10分钟区间不等,最终均可进入无频繁重平衡的稳定状态,重平衡期间的吞吐量相比调整前有明显提升。
内容的提问来源于stack exchange,提问作者Victor van den Hoven
相关产品推荐
相关产品推荐

