-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] MirrorMaker does not use the consumer bootstrapServer value specified in config.yaml #3949
Comments
Can you share the whole log from the Kafka Mirror Maker pod? It should on the beginning print the configuration we pass to Mirror Maker I think. That should help to investigate it. |
FYI: I do not have any Kafka cluster with SASL PLAIN. But it does not happen to me with SCRAM-SHA-512. So I think the logs from you will be critical to address this. |
Hi Jakub, thanks for your fast reply. This is the output from the creation logs
I changed the authentication type to scram-sha-512 just in case.. but same problem here |
Sorry, but that is not the whole log. On the beginning, when the container starts, our scripts print information about how they configure the Mirror Maker and that is the interesting part. You should see there something like this:
|
Hello Jakub, thanks for your help! I was now able to figure out what the problem was. Root cause of the problem was, that i encoded the password secret with the windows shell. After two days of trying, i figured out that the password secret has to be base64 encoded in a linux environment. Now the MirrorMaker works fine! Thanks for your help and the great work on strimzi! Best Regards |
Describe the bug
Mirror Maker does not use the consumer bootstrapServer value specified in its config.yaml
To Reproduce
kubectl apply -f config.yaml
see the logs of the pod where consumer bootstrap server list is empty:
Note that producer bootstrap server is filled correctly
Expected behavior
bootstrap server list should be filled with the corresponding server from the config.yaml
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: