WEBVTT 00:04.250 --> 00:09.920 We have just successfully produced some messages to our Closter and we have consumed them and we can 00:09.920 --> 00:15.650 verify that everything works smoothly and that means that there was no difference how many brokers are 00:15.650 --> 00:21.390 inside of the class to producers and consumers perform their job, same as before. 00:21.410 --> 00:22.700 So no difference here. 00:23.120 --> 00:28.490 Also, you are able, if you want to connect to specific partition and with data only from a particular 00:28.490 --> 00:30.680 partition by specific consumer. 00:31.010 --> 00:32.900 But we have done that in a previous example. 00:32.930 --> 00:34.940 That's why there was no sense to repeat it here. 00:35.240 --> 00:38.330 Now let's try to explore the details of this topic. 00:38.570 --> 00:45.470 Let's go to our commands, list this one, and let's try to list topics using this command and notice 00:45.470 --> 00:49.260 again that you could adjust the D-line with bootstrap server. 00:49.400 --> 00:50.690 Let's actually do that. 00:51.820 --> 00:59.560 Or this part based here, based here as well, and here we will read details about the topic. 01:00.340 --> 01:04.410 So first, let's list all topics in our Kloster. 01:05.390 --> 01:13.130 New tap sedita to Kafka and Waste Command, and as expected, I go to two topics on the list system 01:13.130 --> 01:15.880 one, consumer upsets and cardstock list. 01:15.890 --> 01:19.520 Now read the tales about Carl Storbeck in this command. 01:19.970 --> 01:22.940 Clear Terminal and paste comment and Antle. 01:24.020 --> 01:31.430 Let me make it a bit smaller, like soul, and as expected, we see that this topic course has five 01:31.430 --> 01:34.630 politicians default obligation of fact or one. 01:34.850 --> 01:39.890 Actually, we have specified this option in this comment when we have created a topic. 01:40.070 --> 01:45.010 But I emphasize that it is not necessary because the obligation factor is by default one. 01:45.410 --> 01:52.760 OK, so so fix segment by its is the same as the four topic in the previous example, and it is one 01:52.760 --> 01:56.480 gigabyte in its maximum size of every log file inside of the partition. 01:56.720 --> 02:02.750 And here below we see information about partitions, and that's where output differs from the output 02:02.750 --> 02:06.630 from the previous example when we had only a single breuker. 02:06.770 --> 02:13.460 Now there are three different brokers and that means that now different partitions allocated on different 02:13.460 --> 02:19.420 Brockhouse and you could understand which brokers set of different partitions by this output. 02:19.460 --> 02:21.080 Let's have a look at Partition Zero. 02:21.350 --> 02:29.000 Its leader is broker number zero and that means that this partition is primarily served by these broker 02:29.000 --> 02:29.890 Wizards' zero. 02:30.200 --> 02:35.810 There was only a single replica and it is this broker itself does because an application of factor is 02:35.810 --> 02:43.400 one and no other brokers have the same partition and in-sync replicas is the same as this. 02:43.550 --> 02:48.560 And it does broker with a zero same relates for all remaining partitions. 02:48.560 --> 02:55.100 For example, this partition is located at the broker with Idea one, and this broker is leader for 02:55.100 --> 02:57.170 this partition, etc.. 02:57.320 --> 02:58.190 All right. 02:58.190 --> 02:59.570 And or with a request. 03:00.320 --> 03:02.190 Also, there was a single replica. 03:02.210 --> 03:06.580 It is this broker itself and it is also in-sync replica as well. 03:07.490 --> 03:07.900 Great. 03:08.090 --> 03:11.090 This whole partitions, widespread spread among different brokers. 03:11.210 --> 03:17.840 And that's how you are able to read details about those partitions, not let's try to simulate a feel 03:17.840 --> 03:24.140 or specific broker inside of the cluster and see what will happen with partitions that the well located 03:24.140 --> 03:25.890 on that failed broker. 03:26.060 --> 03:27.150 I'll see you next. 03:27.170 --> 03:27.580 Bye bye.