Hi,
I see the same.
I just downloaded the Kafka zip and I run:
~/kafka-2.4.0-rc3$ ./bin/connect-mirror-maker.sh
config/connect-mirror-maker.properties
Peter
On Mon, 16 Dec 2019 at 17:14, Ryanne Dolan wrote:
> Hey Jamie, are you running the MM2 connectors on an existing Connect
> cluster, or w
eter, Jamie, can one of you file a jira ticket if you are still seeing
> this? Thanks!
>
> Ryanne
>
> On Fri, Dec 27, 2019 at 12:04 PM Ryanne Dolan
> wrote:
>
> > Thanks Peter, I'll take a look.
> >
> > Ryanne
> >
> > On Fri, Dec 27, 2019, 7
brokers continuously send heartbeat requests, __cluster_metadata will
> keep "updating" even if there are no topic changes.
> Best,
> Chia-Ping
>
>
> Péter Sinóros-Szabó 於 2025年4月18日 週五
> 上午1:30寫道：
>
> > Hi,
> >
> > I'm looking for a way
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
he listener I accessed Kafka through, am I right?
Thanks,
Peter
On Thu, 17 Apr 2025 at 22:59, José Armando García Sancio
wrote:
> 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
> &
