Hi Peter, On Thu, Apr 17, 2025 at 2:44 PM Péter Sinóros-Szabó <peter.sinoros-sz...@wise.com.invalid> wrote: > So we need to see as brokers are stopped and restarted, so that we > get it's new IP and can update it on our service mesh configuration.
Very interesting use case. First, the data stored in the __cluster_metadata-0 partition is internal to Kafka and can change at any time. These changes may break a client that was previously reading this data. It is beneficial to the evolution of Kafka to keep this data and schema internal. Based on your problem, it looks like you are not interested in all of the data stored in the cluster metadata partition but are instead interested in the broker metadata returned in the METADATA response object. The problem with the METADATA rpc is that it cannot be streamed and instead must be queried with some interval. Is your client interested in all of the endpoints exposed by the brokers or only a specific endpoint/listener? Thanks, -- -José
