mm2 sourceConnector config items not applied to mirrored topics #7224
Unanswered
scottc-git
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a few source topics that I've been trying to mirror to Strimzi kafka. Since mm2 did not create topics in the target cluster exactly the same as the source, I've added a few Kafka topic config items to the sourceConnector. And it did create the topics with those configs, however, some time later somebody (the mirrorMaker? Entity|Topic Operator?) sets those back to the Kafka (broker) default! Saw this multiple times.
To be specific, I need to ensure at least the following 3 items are applied to the target topics: replication.factor(3), min.insync.replicas(2) and the message.max.bytes (10M), however, they are set to 3, 1(!), and 10M, respectively. I've also tried defining KafkaTopic yaml resources myself for these topics (I didn't need to) just to ensure I get the correct topic configurations but to no avail.
Here's my simplified MM2 config.
Am I using right config items at right place? Maybe the SMTs are messing up things? Probably not because I do not see the overridden items in /tmp/strimzi-connect.properties.
Question: How am I supposed to set
min.insync.replicas: 2
and how can I ensure these are not reset to Kafka default?Thanks for the help in advance.
Beta Was this translation helpful? Give feedback.
All reactions