That's really good information, I wonder if this whole rebalance strategy from kstreams also applies to kafka connect? I've been experiencing some long delays after deploying a new version of our containers which cause them to be recycled. Thanks
First of all, I declare myself fan number 1 of Gwen Shapira's laugh :) Now the question, do you think is possible to explain how stand by replicas works in Kafka Streams applications? for dummies please. The fact you need to run N instantes plus 1 if you have just 1 stand by replica, what does that mean? that other extra instance of the app needs to be running on the same host? that extra stand by app instance will take the work of other failed/crashed app within the same consumer group/app id? sorry for the long question.
That's really good information, I wonder if this whole rebalance strategy from kstreams also applies to kafka connect? I've been experiencing some long delays after deploying a new version of our containers which cause them to be recycled.
Thanks
another great show keep it up Gwen and the team at Kafka
First of all, I declare myself fan number 1 of Gwen Shapira's laugh :)
Now the question, do you think is possible to explain how stand by replicas works in Kafka Streams applications? for dummies please. The fact you need to run N instantes plus 1 if you have just 1 stand by replica, what does that mean? that other extra instance of the app needs to be running on the same host? that extra stand by app instance will take the work of other failed/crashed app within the same consumer group/app id? sorry for the long question.
Thank You