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
/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 `--zookeeper`.
Does the above explanation match your Kafka setup?
--
Divij Vaidya
On Thu, Dec 8, 2022
Hi Divij,
As this issue manifests after the Kafka controller restart, is there a way to
detect this corrupted Kafka cluster before restarting the controller?
Regards,
Atul
From: Atul Kumar (atkumar3)
Sent: 16 December 2022 18:24
To: atul.ku
Hello Everyone ,
Recently we faced an issue where produce request to one topic was failing on
one of the brokers. On further investigation, we found
"java.lang.ClassCastException: org.apache.kafka.common.TopicPartition" in the
stacktrace. The issue was mitigated by restart the problematic broke
