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
Comments
@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. |
@JumaX Many thanks for your reply. So, it would be helpful that cp-ansible let us to have chroot path in zookeeper.connect property. |
@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. |
@a-narenji Can you please review: #694 |
@domenicbove We checked it in our test environment. |
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.
The text was updated successfully, but these errors were encountered: