Now you understand why a Kafka is called a distributor system because you are able to create a cluster
of brokers with multiple brokers, but if there are multiple brokers inside of the cluster, it becomes
unclear how they maintain state of entire cluster and how they communicate between each other.
And that's where the zookeeper comes in.
Zookeeper was also developed by Abhijeet is called basically Apache's or Jibaro, and it is used not
just in conjunction with a Kafka.
It is also used with Apache Hadoop, for example, or Apache Solar and Apache.
Kafka broker will not even start without active connection to Zookeeper.
That's why Zookeeper is a mandatory part of a pasture ecosystem and main responsibilities of zookeeper
in case when it is used with a bicycle are forming.
First of all, it maintains a list of active brockers.
It means that at any moment of time it knows which brokers are active and Dilli and which Helfeld also
zookeeper ALLEX controller.
We will talk about what is control a bit later.
But Controller is elected among brokers in a cluster and there was just a single controller in every
cluster.
Also, Zookeeper manages configuration of the topics and partitions.
It means that when you create any topic in a Kafka colostrum, it is created basically at a zookeeper.
And Zookeeper distributes this configuration to all brokers in the class.
That's the way the zookeeper is needed and that's what it does in a Kafka ecosystem.
But now you may ask my question, but what if this single zookeeper Ostrer, fails how brokers, producers
and consumers will continue their operations?
You are able to create a cluster of zookeepers and let me talk about it in the next lecture by.