Hi David, Thanks for your question. Here's one elderly JIRA I've unearthed which is related https://issues.apache.org/jira/browse/KAFKA-15828.
I am also aware of suspected problems in the networking for cloud providers which occasionally seem to route connections to the wrong place. The KIP is aiming to get some basic diagnosis and recovery into the Kafka protocol where today there is none. As you can imagine, there is total mayhem when a client confidently thinks it's talking to one broker when actually it's talking to quite another. Diagnosis of this kind of problem would really help in getting to the bottom of rare issues such as these. Thanks, Andrew On 2026/02/11 16:12:50 David Arthur wrote: > Thanks for the KIP, Andrew. I'm all for making the client more robust > against networking and deployment weirdness > > I'm not sure I fully grok the scenario you are covering here. It sounds > like you're guarding against a hostname being reused by a different broker. > Does the client not learn about the new broker hostnames when it refreshes > metadata periodically? > > -David > > On Thu, Nov 20, 2025 at 5:59 AM Andrew Schofield <[email protected]> > wrote: > > > Hi, > > I would like to start discussion of a new KIP for detecting and handling > > misrouted connections from Kafka clients. The Kafka protocol does not > > contain any information for working out when the broker metadata > > information in a client is inconsistent or stale. This KIP proposes a way > > to address this. > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1242%3A+Detection+and+handling+of+misrouted+connections > > > > Thanks, > > Andrew > > > > > -- > David Arthur >
