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

Remove ZooKeeper from Cruise Control since Kafka 4.0 will not support it #2243

Open
egyedt opened this issue Jan 29, 2025 · 0 comments · May be fixed by #2244
Open

Remove ZooKeeper from Cruise Control since Kafka 4.0 will not support it #2243

egyedt opened this issue Jan 29, 2025 · 0 comments · May be fixed by #2244

Comments

@egyedt
Copy link
Contributor

egyedt commented Jan 29, 2025

Remove ZooKeeper from Cruise Control since Kafka 4.0 will not support it.
Cruise Control use ZK in production codes and in test codes as well. The most of the production codes - where ZK is in use - are deprecated or not defaults and there is already another solution. Furthermore, Cruise Control is able to work without ZK in its current state.
The tests are heavily depends on ZK since the integration ones are using Kafka brokers with ZK as metadata store, additionally ZK client is also used, which can be replaced with Kafka AdminClient.
We should remove ZK from Cruise Control, since CC not requires it and ZK will be removed from Kafka as well.

@egyedt egyedt linked a pull request Jan 29, 2025 that will close this issue
6 tasks
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.

1 participant