卡夫卡0.9.0上Zookeeper的使用 [英] Zookeeper usage on Kafka 0.9.0

问题描述

有人可以在kafka 0.9.0中告诉我(保存kafka中的偏移量并使用新的使用者)，动物园管理员执行的哪些功能可能需要大量资源?这些资源会在数据高峰期间波动很大吗?或仅当集群中发生某些故障时?

Can someone tell me in kafka 0.9.0 (saving the offsets in kafka and using the new consumer) what are the functions that zookeeper perform that may require lot of resources? will this resources fluctuate a lot in a data spike? or only if something crashes in the cluster?

推荐答案

您已经说过，生产者或消费者在0.9.0中不再使用ZooKeeper.但是，Kafka的大部分元数据都存储在ZooKeeper中-主题，分区，副本，ISR，代理等.单个生产或消费不会与ZooKeeper交互.相反，ZooKeeper在更广泛的"操作中进行交互:添加新的代理，添加新主题，从失败的代理中恢复，从失败的控制器中恢复等.此外，代理与ZooKeeper一起跳动，允许ZooKeeper知道代理是否失败.

As you've said, ZooKeeper is no longer used by the producer or consumer in 0.9.0. However, Kafka stores much of its metadata in ZooKeeper -- topics, partitions, replicas, the ISR, brokers, etc. A single produce or consume does not interact with ZooKeeper. Instead, ZooKeeper is interacted with in "broader" operations: adding a new broker, adding a new topic, recovering from a failed broker, recovering from a failed controller, etc. Also, brokers heartbeat with ZooKeeper, allowing ZooKeeper to know if a broker fails.

通常，在0.9.0中，只有拥有庞大的集群，大量分区或非常小的ZooKeeper节点时，ZooKeeper才会成为性能瓶颈.

In general, in 0.9.0, ZooKeeper will only be a performance bottleneck if you have a massive cluster, a massive number of partitions, or very "small" ZooKeeper nodes.

这篇关于卡夫卡0.9.0上Zookeeper的使用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！