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

Replace AdminZkClient with AdminClient #1415

Closed
Lincong opened this issue Dec 9, 2020 · 11 comments · Fixed by #1569
Closed

Replace AdminZkClient with AdminClient #1415

Lincong opened this issue Dec 9, 2020 · 11 comments · Fixed by #1569
Assignees
Labels
kafka-behavior-change Issues due to code changes in Kafka code robustness Makes the project tolerate or handle perturbations.

Comments

@Lincong
Copy link
Contributor

Lincong commented Dec 9, 2020

Motivations:

  1. AdminZkClient gets information from Zookeeper which will be removed from Kafka as a dependency (KIP-500).

  2. Java doc of AdminZkClient class says This is an internal class and no compatibility guarantees are provided, see org.apache.kafka.clients.admin.AdminClient for publicly supported APIs.

@Lincong Lincong added kafka-behavior-change Issues due to code changes in Kafka code robustness Makes the project tolerate or handle perturbations. labels Dec 9, 2020
@Lincong Lincong assigned Lincong and unassigned Lincong Dec 9, 2020
@ghost
Copy link

ghost commented Dec 9, 2020

@Lincong can I take this one on? Or did you mean to assign it to yourself?

@Lincong
Copy link
Contributor Author

Lincong commented Dec 9, 2020

@Lincong can I take this one on? Or did you mean to assign it to yourself?

Hi Jacob, I am glad that you want to take on this issue, and of course, you can. Just want to share some of my opinions regarding the implementation to resolve this issue.

  1. In the codebase, find all places where AdminZkClient is used and replace them all since the goal is to completely migrate to AdminClient.

  2. Note that there is an API-level semantics difference in AdminZkClient vs AdminClient regarding topic config changes. In AdminClient, the topic config change is incremental (diff-based) whereas AdminZkClient overrides topic config.

Let me know if you have any questions or have any things you want to discuss with me while you are implementing it. Thanks!

@ghost
Copy link

ghost commented Dec 9, 2020

Will do. Thank you for the info.

@Lincong Lincong assigned ghost Dec 10, 2020
@tomncooper
Copy link
Contributor

@JacobHell Did you manage to complete this work?

@ghost
Copy link

ghost commented May 15, 2021

@tomncooper no, it can be reassigned. Apologies.

@tomncooper
Copy link
Contributor

I would be happy to give this issue a try, if no one else is working on it currently?

@efeg
Copy link
Collaborator

efeg commented May 19, 2021

Thanks for working on this @tomncooper -- I reassigned the issue to you.

@efeg
Copy link
Collaborator

efeg commented Aug 6, 2021

@tomncooper After #1644 is merged, the only key remaining item will be the use of AdminZkClient for replication throttle. Can I assume that you will be working on that part?

@tomncooper
Copy link
Contributor

Hi @efeg, yes I will take that on.

@tmcgrath
Copy link

Question to confirm my understanding of this work. Once complete, this will remove the need to configure ZK access. If so, great!

@erikgb
Copy link

erikgb commented May 23, 2022

This issue seems to be fixed, ref. https://github.com/linkedin/cruise-control/wiki/Run-without-ZooKeeper. Close issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kafka-behavior-change Issues due to code changes in Kafka code robustness Makes the project tolerate or handle perturbations.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants