We have just successfully created the new topic in our last hour, and topic name is Month Replication
Factor was said to three and wanted it is equal to seven.
And now let's quickly open up blogs for those where our messages will be stored on our computer and
observe which partitions were created on which broadcast.
And now in our set up for this topic, we should see the same politicians on different broadcasts.
Thus, due to the replication factor equal to three, you'll remember that if there are replicas, then
one of the broadcasts is leader for specific partition and all the remaining brokers are full of words
and they simply accept the right request from leader and they don't.
Producers and consumers for particular partition where they are not leaders.
So let's observe this in our example and see what happened actually on average of the broadcast.
OK, let's see to before them.
So let's drop them and let's open this folder in finder.
In my case, and as in a previous example, I see here separate the folders for logs of every brolga.
And thus because we have configured so in the configuration files where every broker and let's not expand,
for example, this folder with logs for Breuker or Zero.
And now I see that this broker has created seven sub folders for different partitions for topic month
from a zero deal six.
Let's expand the also subfolder of the next Borkur with add one and same picture here.
It has created seven folders for every partition of the month and you may guess that same actually happened
for Breuker with added two.
Yes, here it is also seven partitions for topic month and that's fully correct.
In total we have set up seven partitions and obligation factor is three.
And that means that for every partition there should be in total three different replicas, including
leader, of course, and that's what we see here.
Every partition was created on each of our brokers in the Gloster grade.
But it's important to understand that for every partition, only a single broker is selected as leader
and only a single broker serros, producers and consumers that want to interact with this particular
partition.
And all the remaining brokers are just of and they simply synchronize messages with leader in order
to prove that.
Let's try to read the details about this topic.
For that, let's go to our file with commands and find a command that will list for all topics.
This one, let's go up it.
Go to a folder again.
Sidiq Afkham clear terminal based command.
Let's list all topics.
And at the moment I see only a single topic Mom recounted in examples before.
We have seen all the consumer of s topic, but for now it is absent.
My question to you.
Why is it absent?
You are right.
Consumer offsets topic is automatically created after first connection of consumer to the Gloster.
We haven't yet connected to the glass to intimate, yet produced and consumed any messages.
That's why this consumer of this topic is absent at the moment.
OK, now let's read the tales about this topic.
Let's go back to our final magic file was All Commands.
Let me open this comment and show that here our topic is math and based command here.
Let me make it a bit smaller.
And here we are, we see details about Dobek month partition count is equal to seven, reduplication
factor is equal to three and segment bias is by default against one gigabyte.
Great.
And here we see a difference from the output in previous example.
Let's observe the tables for partition zero.
You see here that the leader ID is two.
That means that the broker with the two is, let's say, primary broker for this partition and it is
responsible for all read and write requests from producers and consumers.
And this broker, with added two, is responsible for replication of all messages to all followers.
And here in the next column, you see a list of replicas and here you see I.D. of all brokers and first
one is to so to zero one, first comes actually leader.
And this is equal to this idea here in this column.
And afterwards, we see I.D. of two women brokers, zero and one.
And that means that those two brokers fall over for this partition partition with zero.
Also in this column, you see in-sync replicas and here you see a list of ideas of the brokers that
are fully synchronized for this partition.
We haven't yet produced any messages and all brokers are up and running.
And that's why here and here you'll see actually the same list of ideas.
Later on, we will play with the set up and try to bring one of the brokers down and observe what will
change here in this output.
But for now, we could say that the hourglass is fully healthy.
All brokers are up and running and all partitions are available for read and write operations.
That's how picture looks like for our new topic month when it has multiple replicas configured.
And again, in total, we have seven of partitions, wonderful lisinopril sit and next to let's try
to produce some messages.
And Delonge Kafka console consumer and console producer.
So see you next.
Bye bye.