Hey Daniel,
it seems to work fine as well, but it's spamming the error messages
multiple times per second into the logs making it hard to put monitoring on
the logs and also just steadily growing disk space xD
I've been looking through the code trying to figure out how to disable or
change it ...
Hello,
I have noticed a problem which I have also discussed with RedHat
(https://issues.redhat.com/browse/DBZ-4521):
Prerequisites:
* Debezium connector with heartbeat configuration (
"heartbeat.topics.prefix" is set)
* Heartbeat topic on Kafka side does NOT exists
* Parameter auto.
i'm curious at what point can 3.x be production ready?
On Mon, Jan 24, 2022 at 10:04 AM David Jacot wrote:
> The Apache Kafka community is pleased to announce the release for
> Apache Kafka 3.1.0.
>
> It is a major release that includes many new features, including:
>
> * Apache Kafka supports J
Thanks Ed.
On Mon, Jan 24, 2022 at 2:21 PM Edward Capriolo
wrote:
> In general you can delete log4j1.jar
> Replace with log4jcore_2.17.1.jar
> And log4japi_2.17.1.jar
>
> Ed
>
> On Monday, January 24, 2022, Men Lim wrote:
>
> > Is there a write out of the steps that need to be taken?
> >
> > On
Hi,
This is possible since Kafka 3.0. You can use the
"offset-syncs.topic.location" configuration on both the source and
checkpoint connectors to move the offset-syncs topic to the target
cluster.
See
https://cwiki.apache.org/confluence/display/KAFKA/KIP-716%3A+Allow+configuring+the+location+of+
Kafka 3.x is production ready if you are running it with Zookeeper
If you are running it in KRaft mode without Zookeeper that set up is not
yet recommended for production scenarios
I hope this clarifies your concerns
On Wed, Jan 26, 2022 at 9:50 AM Men Lim wrote:
> i'm curious at what point
