We have just successfully produced some messages to our Closter and we have consumed them and we can
verify that everything works smoothly and that means that there was no difference how many brokers are
inside of the class to producers and consumers perform their job, same as before.
So no difference here.
Also, you are able, if you want to connect to specific partition and with data only from a particular
partition by specific consumer.
But we have done that in a previous example.
That's why there was no sense to repeat it here.
Now let's try to explore the details of this topic.
Let's go to our commands, list this one, and let's try to list topics using this command and notice
again that you could adjust the D-line with bootstrap server.
Let's actually do that.
Or this part based here, based here as well, and here we will read details about the topic.
So first, let's list all topics in our Kloster.
New tap sedita to Kafka and Waste Command, and as expected, I go to two topics on the list system
one, consumer upsets and cardstock list.
Now read the tales about Carl Storbeck in this command.
Clear Terminal and paste comment and Antle.
Let me make it a bit smaller, like soul, and as expected, we see that this topic course has five
politicians default obligation of fact or one.
Actually, we have specified this option in this comment when we have created a topic.
But I emphasize that it is not necessary because the obligation factor is by default one.
OK, so so fix segment by its is the same as the four topic in the previous example, and it is one
gigabyte in its maximum size of every log file inside of the partition.
And here below we see information about partitions, and that's where output differs from the output
from the previous example when we had only a single breuker.
Now there are three different brokers and that means that now different partitions allocated on different
Brockhouse and you could understand which brokers set of different partitions by this output.
Let's have a look at Partition Zero.
Its leader is broker number zero and that means that this partition is primarily served by these broker
Wizards' zero.
There was only a single replica and it is this broker itself does because an application of factor is
one and no other brokers have the same partition and in-sync replicas is the same as this.
And it does broker with a zero same relates for all remaining partitions.
For example, this partition is located at the broker with Idea one, and this broker is leader for
this partition, etc..
All right.
And or with a request.
Also, there was a single replica.
It is this broker itself and it is also in-sync replica as well.
Great.
This whole partitions, widespread spread among different brokers.
And that's how you are able to read details about those partitions, not let's try to simulate a feel
or specific broker inside of the cluster and see what will happen with partitions that the well located
on that failed broker.
I'll see you next.
Bye bye.