admin管理员组

文章数量:1390410

I have an application with multi-cluster binder that reads from one Kafka cluster and produces message to another Kafka cluster. At some point I started to receive such log messages:

1 --- [pool-2-thread-1] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer-some-10, groupId=some] The following partitions still have unstable offsets which are not cleared on the broker side: [topicName-14], this could be either transactional offsets waiting for completion, or normal offsets waiting for replication after appending to local log

I have other applications that read from that cluster too and topic too, but no such error provided. I have no access to producer for that topic, so I do not know if even transactions are used there. The question is, is it problem with messages that producer wrote, or may my consumer be slow to commmit offsets? Or it is just a broker issue?

本文标签： javaReceiving unstable offsets using Spring Cloud Kafka BinderStack Overflow

版权声明：本文标题：java - Receiving unstable offsets using Spring Cloud Kafka Binder - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1744665962a2618533.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。