hi all,
I'm actually interested in all the advertised listener configs
It's a coincidence that we have a KIP (
https://cwiki.apache.org/confluence/x/PZFEF) which tries to get the
advertised listeners by using DESCRIBE_CONFIGS.
Maybe you could give it a try as well.
Best,
Chia-Ping
José Armand
Hi Peter,
On Fri, Apr 25, 2025 at 10:14 AM Péter Sinóros-Szabó
wrote:
> I'm actually interested in all the advertised listener configs, we use a
> few of them. As I see the metadata response will contain only one
> listener's data, the listener I accessed Kafka through, am I right?
That's correc
Hi José,
> Is your client interested in all of the endpoints exposed by the brokers
or only a specific endpoint/listener?
I'm actually interested in all the advertised listener configs, we use a
few of them. As I see the metadata response will contain only one
listener's data, the listener I acces
Hi Peter,
On Thu, Apr 17, 2025 at 2:44 PM Péter Sinóros-Szabó
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
Hi Chia-Ping,
> Pardon me, what is the purpose of monitoring __cluster_metadata?
We run one of our Kafka clusters on Kubernetes, where the IP address of the
pods running the broker changes every time the pod is restarted for any
reason. So we need to see as brokers are stopped and restarted, so th
hi Peter
Pardon me, what is the purpose of monitoring __cluster_metadata? Are you
looking to observe topic changes or other cluster modifications?
As brokers continuously send heartbeat requests, __cluster_metadata will
keep "updating" even if there are no topic changes.
Best,
Chia-Ping
Péter S
Hi,
I'm looking for a way to consume the cluster metadata updates when using
KRaft. I thought I'll just consume the __cluster_metadata topic, but as I
see that's not possible, at least I didn't manage to do that with the
console consumer.
I know we have the dump tool or the metadata shell to quer
