Skip to content
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

Configure Kafka broker to use Zookeeper chroot path #691

Closed
a-narenji opened this issue Jun 14, 2021 · 5 comments · Fixed by #694
Closed

Configure Kafka broker to use Zookeeper chroot path #691

a-narenji opened this issue Jun 14, 2021 · 5 comments · Fixed by #694

Comments

@a-narenji
Copy link

We need to configure Kafka brokers to use Zookeeper chroot path. By default, Kafka creates znodes in root of Zookeeper.
In order to separate app and Kafka configurations, it is necessary to set different chroot path for Kafka.

Is it possible to have Kafka with chroot Zookeeper path provisioned by cp-ansible?

As an example. we need cp-ansible to configure zookeeper.connect to have a value like: hostname1:port1,hostname2:port2,hostname3:port3/chroot/path.

@a-narenji a-narenji changed the title Configure kafka broker to use zookeeper chroot path Configure Kafka broker to use Zookeeper chroot path Jun 14, 2021
@JumaX
Copy link
Contributor

JumaX commented Jun 14, 2021

@a-narenji Are you using an existing zookeeper cluster for multiple applications? If so, we generally do not recommend this, we recommend you let cp-ansible install zookeeper and manage it. We cannot guarantee that whichever version you may already be running is compatible etc.

You can override all configurations via custom properties as per our documentation here:

https://docs.confluent.io/ansible/current/ansible-configure.html#set-custom-component-properties

So you could set the properties to your desired configuration on the Broker, however if we are not managing zookeeper for you, you would need to configure that yourself manually.

@a-narenji
Copy link
Author

@JumaX Many thanks for your reply.
We are not using existing Zookeeper cluster, and we use the same Zookeeper which cp-ansible set it up for us.
Our develop team may need to use Zookeeper for another purpose, and it may not be reasonable to have a second Zookeeper cluster dedicated to develop team requirements.

So, it would be helpful that cp-ansible let us to have chroot path in zookeeper.connect property.
Additionally, since we need to enable SASL, it is not enough to change zookeeper.connect only, but also, it is required to change Create SCRAM Users and Create SCRAM 256 Users tasks in such a way that cp-ansible be able to create SCRAM users to use Zookeeper chroot path.

@JumaX
Copy link
Contributor

JumaX commented Jun 15, 2021

@a-narenji Thanks for the additional details. Unfortunately, at this time we do not support this configuration. Specifically around the scram users. Of additional note, is that Zookeeper is being removed as a kafka dependency soon, so we will review this and see if it makes sense to allow this modification with zookeeper for a future release.

@domenicbove domenicbove linked a pull request Jun 21, 2021 that will close this issue
12 tasks
@domenicbove
Copy link
Contributor

@a-narenji Can you please review: #694

@a-narenji
Copy link
Author

a-narenji commented Jun 22, 2021

@domenicbove We checked it in our test environment.
It worked great.
Many thanks for adding this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants