Kafka Streams 2.7.1 to 3.3.1 rolling upgrade

Hi Team, I am trying to upgrade my Kaka Streams application from 2.7.1 to 3.3.1. Brokers are running on Kafka 2.7.1. The plan is to upgrade the clients first and then then brokers I have already enabled the static membership in our application so that we I am not expecting a rebalance. Below are

producer purgatory

Hi guys, I am loadtesting a couple clusters one with local ssd disks and another one with ceph. Both clusters have the same amount of cpu/ram and they are configured the same way. im sending the same amount of messages and producing with linger.ms=0 and acks=all besides seeing higuer latencies o

Re: producer purgatory

thank you! On Mon, Feb 27, 2023 at 12:37 PM David Ballano Fernandez < dfernan...@demonware.net> wrote: > Hi guys, > > I am loadtesting a couple clusters one with local ssd disks and another > one with ceph. > > Both clusters have the same amount of cpu/ram and they are configured the > same way.

Re: Kafka Streams 2.7.1 to 3.3.1 rolling upgrade

Hmmm... that's interesting... It seems that Kafka Streams "version probing" does not play well static group membership... Sounds like a "bug" to me -- well, more like a missing integration. Not sure right now, if/how we could fix it. Can you file a ticket? For now, I don't think you can do