WEBVTT 00:04.400 --> 00:09.380 No, you know what happened in coffeecake last hour under the hood when we have entered this command 00:09.560 --> 00:15.380 that actually created Utopia, let's not try to read the details about this city. 00:15.380 --> 00:19.970 Storbeck For that, let's Sidis again to Kafka, FALDER City to Kafka. 00:20.910 --> 00:27.420 Clear terminal and no, let's run again, same script topics, but with another option, that's the 00:27.630 --> 00:36.420 least been topics Topix as age and here will be optioned list and afterwards we need to specify, same 00:36.420 --> 00:38.460 as before, a bootstrap. 00:38.460 --> 00:40.520 Sabra, also keep ourselves. 00:40.980 --> 00:44.430 Let's try to specify connections between of Zookeeper. 00:44.640 --> 00:46.920 For that, let's use zookeeper option. 00:48.900 --> 00:54.660 And here will be address of connection to Ozaukee Prospero, remember that the zookeeper is running 00:54.660 --> 00:58.590 at Port two one eight one, so he'll type two one eight one. 00:58.740 --> 01:03.300 And let's press enter and you'll see a list of the topics in Kafka class. 01:03.510 --> 01:06.320 And now there was just a single topic called seeds. 01:06.780 --> 01:08.230 That's what this command does. 01:08.460 --> 01:14.760 You could always use this list option in order to list all available topics that exist in Kafka. 01:14.760 --> 01:21.510 Gloucester also noticed that we have just used Zookeeper option instead of bootstrap Sarah. 01:21.690 --> 01:29.160 And that means that you are able to connect to Kafka Gloster either via Zookeeper or any of the Kafka 01:29.160 --> 01:29.820 Saras. 01:30.460 --> 01:34.410 OK, let's now read the details about this topic called Citius. 01:34.710 --> 01:36.750 For that, let's use another option. 01:36.750 --> 01:41.280 Does best describe type same command Beenz less COFCO. 01:41.700 --> 01:43.200 Topics nutsedge. 01:43.470 --> 01:44.970 Next comes describe. 01:46.320 --> 01:52.320 Next comes same as before, as a sort of bootstrap, Sarah, let's again specify zookeeper. 01:53.980 --> 01:54.940 Localhost. 01:56.000 --> 02:02.810 Two one eight one, and the next there comes another named argument, name of the topic you want to 02:02.810 --> 02:03.930 read details about. 02:04.490 --> 02:06.490 So let's look at this next topic. 02:07.680 --> 02:11.580 And here comes the name of the topic, Cities and Lesperance Enter. 02:12.850 --> 02:18.370 And here with our configuration details for this topic, let me make it a bit smaller to feed it to 02:18.370 --> 02:18.940 the screen. 02:19.920 --> 02:27.300 Like this and do we see such information topic name cities next competition, count one, and you already 02:27.300 --> 02:28.080 know what is that? 02:28.410 --> 02:34.560 That is actually quantity of different folders where messages of this topic will be stored and by default, 02:34.710 --> 02:36.090 this quantity is one. 02:36.600 --> 02:39.180 Next comes and others are new for you. 02:39.180 --> 02:41.460 Parameter replication factor one. 02:41.880 --> 02:44.640 What does this parameter mean at the moment? 02:44.640 --> 02:51.600 Our coffeecake last year has only single broker and if the seller will become unavailable for some reason, 02:51.810 --> 02:58.190 then nobody will be able to store new messages that will be arrive from producers and consumers will 02:58.200 --> 03:00.390 be able to read data from the server. 03:00.990 --> 03:03.690 And that's why replication factor is used. 03:04.050 --> 03:10.230 If there are multiple brokers in the Gloucester, you are able to replicate every message that arrives 03:10.230 --> 03:17.280 to topic in our case, see this topic and replication factor of how many times each message will be 03:17.280 --> 03:18.150 replicated. 03:18.570 --> 03:24.450 And in our case, this parameter is set to default value one because we have only one server and only 03:24.450 --> 03:28.290 one server will save every single message in the topic. 03:28.770 --> 03:34.950 But if there were, for example, three s in this cluster, you can set replication a factor to three 03:35.130 --> 03:42.790 and every message in this topic will be stored on every of three servers for the purposes, of course. 03:43.170 --> 03:45.630 OK, that's replication facto below. 03:45.630 --> 03:48.630 After this line, you'll see this line with details. 03:48.630 --> 03:52.050 For every partition, here comes number of partition. 03:52.050 --> 03:57.650 And you know that partition numbers start from zero zero one two and so on. 03:57.900 --> 04:02.520 Next comes information about leader grammaticus and in-sync replicas. 04:02.760 --> 04:05.400 And everywhere you see here, Namba zero. 04:05.640 --> 04:08.280 And it is basically number of the broker. 04:08.520 --> 04:12.890 And in our case, we have only a single broker with Zero Raqib. 04:13.050 --> 04:16.680 This configuration parameter broker ID zero, this one. 04:17.190 --> 04:20.640 And that is exactly that number that you see here in those fields. 04:20.970 --> 04:27.830 And that means that every partition must have at least one leader, leader, broker in our case. 04:27.840 --> 04:33.540 Again, we have only a single broker, and that's why he is leader for this partition partition number 04:33.540 --> 04:33.980 zero. 04:34.650 --> 04:36.750 We will get back to this later on for sure. 04:36.960 --> 04:40.200 But no, you should remember that we describe argument. 04:40.320 --> 04:43.590 You are able to read the details about each topic. 04:43.590 --> 04:49.750 In our case, we have only a single topic and you could list all topics in the Kafka cluster by using 04:49.750 --> 04:50.720 the least option. 04:51.210 --> 04:52.770 OK, guys, that's all for this one. 04:52.770 --> 04:58.020 And the next day we could try to send a very strong message to this topic, see this topic. 04:58.350 --> 05:04.740 And for that, we need to have producer, luckily Kafka sheep, Swiss built in consumers and producers 05:04.890 --> 05:11.220 that allocated in Benfold and they are also producer and Kafka Council consumer. 05:11.310 --> 05:16.320 And we are able easily use them in order to produce and consume Kafka messages. 05:16.590 --> 05:20.190 And let's produce some messages for C this topic in the next lecture. 05:20.220 --> 05:20.700 Bye bye.