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

View zookeeper nodes #51

Closed
TrumanDu opened this issue May 19, 2020 · 1 comment
Closed

View zookeeper nodes #51

TrumanDu opened this issue May 19, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@TrumanDu
Copy link
Contributor

No description provided.

@TrumanDu TrumanDu changed the title View zookeeper node View zookeeper nodes May 19, 2020
@TrumanDu TrumanDu added the enhancement New feature or request label May 19, 2020
@TrumanDu
Copy link
Contributor Author

KIP-500 有了新的进展
用过 Kafka 的用户应该清楚,Kafka 的 Broker、topic 以及分区相关的信息是存放在 Apache Zookeeper 中的,Apache Zookeeper 是一个独立的系统,有其独立的存储,为了 Kafka 集群能够更好地运行,开发者们必须对 Kafka 和 Zookeeper 两个系统都很熟悉,这在一定程度上是增加了我们的负担。为了减少使用者的负担,KIP-500 提议将之前存储在 Zookeeper 里面的东西全部移到 Kafka 集群内部维护,也就是说未来 Kafka 不需要依赖 Zookeeper 即可运行。

Apache Kafka 2.5.0 版本对这项工作有了新的进展,比如 KIP-555 中解决管理员工具中不再需要请求 Zookeeper,KIP-543 中使得动态配置不再需要请求 Zookeeper。

KIP-500 是一个大功能,它的最后解决需要在未来几个版本才能体现。

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

No branches or pull requests

1 participant