Re: same keys appearing in state stores on different pods when using branches in kafka streams

Thanks John R. I am adding John Brackin to this thread, who can provide further details of topology description On Tue, Dec 6, 2022 at 8:28 AM John Roesler wrote: > Hi Pushkar, > > I'm sorry for the delay. I'm afraid I'm having trouble picturing the > situation. Can you provide the topology des

Brokers not re-joining the ISR list and stuck at started until all the brokers restart

Hi, We are upgrading a 3 broker cluster (1001,1002,1003) from 3.1.0 to 3.2.0. During upgrade, it is noticed that when 1003 is restarted, it doesn't join back the ISR list and the broker is stuck. Same is the case with 1002. Only when 1001 is restarted, 1003,1002 re-join the ISR list and start repli

Re: Critical bug in Kafka 2.8.1 | topic Id in memory: <> does not match the topic Id for partition <> provided in the request: <>.

Hi Atul There is a known bug which has similar symptoms that you observed. See: https://issues.apache.org/jira/browse/KAFKA-14190 The bug manifests when you use a client < 2.8.0 with `--zookeeper` flag. It could be avoided by either upgrading the client or by using `--bootstrap-server` instead of

Critical bug in Kafka 2.8.1 | topic Id in memory: <> does not match the topic Id for partition <> provided in the request: <>.

Hello everyone, We are using Kafka 2.8.1, and recently while rolling restart of one of our clusters, we encountered the following issue on the Kafka cluster topic Id in memory: <> does not match the topic Id for partition <> provided in the request: <>.  All the produce requests to the imp

Kafka Protocol & Collision/Replay Attacks

I recently created a Threat Model for an application I am working on using Microsoft's Threat Modelling Tool. It highlight two potential threats in relation to the use of the Kafka Protocol