MM2 and Kafka batch failure during topic creation

Hi Team,   We are trying to set MM2 syncbetween 2 clusters (Active\Passive) We have ~3000 topics Using CFK clusters 7.3.0   The problem MM2 tries to create in 1 batchtopics on target cluster (~3000)   In the broker's logs, there is an error   Could not create topicactive-north-2316.

Re: MM2 and Kafka batch failure during topic creation

Hi Team,   We are trying to set MM2 syncbetween 2 clusters (Active\Passive) We have ~3000 topics Using CFK clusters 7.3.0   The problem MM2 tries to create in 1 batchtopics on target cluster (~3000)   In the broker's logs, there is an error   Could not create topicactive-north-2

Re: MM2 and Kafka batch failure during topic creation

Hi, We faced a similar problem when mirroring huge amounts of topics and partitions . Kafka version 3.7.2 We saw an error of BoundedListTooLong Excpetion in t

Re: OAUTH ISSUE | Kafka v3.7.1

Hi Ashish, I'm glad you were able to get it working! :) Reply to your questions below... On Mon, Mar 31, 2025, at 10:19 PM, ashish sood wrote: > Hi Kirk, > > I managed to get it running finally. > > > *Server.properties* > > listeners=SASL_PLAINTEXT://:9093 > advertised.listeners=SASL_PLAINT

Re: Kafka process fails to start when special character is present in Keystore password in SSL encryption and SASL authentication

Hello Kafka users, We are really stuck in this issue where we cannot use the special character in the keystore (and truststore) password from the shell. We would we grateful for any possible solution. Regards, Deepak From: Deepak Jain Sent: Friday, March 28,

Re: OAUTH ISSUE | Kafka v3.7.1

Hi Kirk, The current setup of Auth0 for authentication and ACL for authorization works for me however I was exploring how best we can leverage oAuth both for authentication and Authorization both without writing custom classes. Regards Ashish On Wed, Apr 2, 2025 at 6:16 AM Kirk True wrote: > H

KRaft controller disaster recovery

Consider the following Kafka controller setup. There are three controllers c1, c2 and c3, each on its own hardware. All controllers are voters and let’s assume c1 is the leader. Assume new servers can be added as needed to replace broken one, but broken/lost servers cannot be brought back. If a new

Re: MM2 and Kafka batch failure during topic creation

Thanks, Vruttant, for sharing.   it means we need to have a few MM2 deployments, onlybecause the first step is failing due to the batch limit. It would be more nice if MM2 will have some approach forbatch size on this phase     On Tuesday, April 1, 2025 at 01:13:57 PM GMT+3,