> do you recall the purpose of [...] renameTopicPartition [?]
A's topic1 and B's a.topic1 should be the same data (minus replication
lag). You can't consume a record in a.topic1 that hasn't been replicated
yet -- a remote topic by definition does not have any records that MM2
didn't put there. So
Hi Jeroen,
I'm glad you're experimenting with MM2, and I hope we can give you
some more context to explain what you're seeing.
> I wrote a small program to produce these offset syncs for the prefixed
> topic, and this successfully triggers the Checkpoint connector to start
> replicating the
Hello All,
I am trying to set up Kafka(v3.6.1) to use mTLS
authentication/authorization for *inter broker* communication but currently
server.properties doesn't allow me to set a key store that contains client
private key/certificate. I did try supplying a keystore to Kafka that
contains both TLS
I don't see a need for this. What additional information does this provide
over what can be found via a quick google search?
My primary concern is that we are getting in the business of listing
vendors in the project site which brings it's own complications without
adding much additional value
Hi,
After starting a first thread on this topic
(https://lists.apache.org/thread/kkox33rhtjcdr5zztq3lzj7c5s7k9wsr), I would
like to propose a PR:
https://github.com/apache/kafka-site/pull/577
The purpose of this proposal is to help users to find support for sla,
training,
Hello,
Currently, I have a capacity issue with my current kafka cluster where in
the existing EBS volume is proving insufficient for the new load of
incoming data.
I need to find a solution to persist more data in my cluster and I see two
options
- one to vertically scale volume size
Hi,
I worked on the website to add a commercial support page as discussed and here
a starting PR:
https://github.com/apache/kafka-site/pull/577
For now I just add one company but everybody can add some by providing a PR. If
people want me to add other you can reply to this thread because as
