WEBVTT 00:04.450 --> 00:10.780 No less great new topic, cold pair of doom, and we will launch new consumer in specific a consumer 00:10.780 --> 00:16.780 group, and afterwards we will try to launch producer performance, a test tool and while it will be 00:16.780 --> 00:18.260 producing random messages. 00:18.400 --> 00:21.550 We will try to read the details about specific consumer group. 00:21.970 --> 00:23.730 Let me close this tab. 00:23.950 --> 00:25.810 Let me close this tab as well. 00:25.810 --> 00:33.220 And let's stop this consumer like this and the clear terminal here and our coffee brokers will be still 00:33.220 --> 00:33.670 run. 00:34.150 --> 00:41.860 OK, let's now create a new topic and I'll create a picture of two and let's say quantity of partitions 00:41.860 --> 00:43.120 will be just three. 00:43.510 --> 00:46.840 And let me copy this command based here. 00:48.820 --> 00:55.510 Topic was created and now let's start the consumer into specific consumer group and the consumer will 00:55.510 --> 00:56.650 read from this topic. 00:56.670 --> 01:03.310 Parador, let me scroll down to the comment where we could start consumer in specific group here with 01:03.310 --> 01:03.630 this. 01:03.850 --> 01:11.370 And here we will read from topic pair of Doom and the group, let's say, will be better performance 01:11.390 --> 01:11.680 group. 01:12.010 --> 01:15.280 And let me copy this entire command. 01:15.430 --> 01:18.790 Go here, clear Tamino and let's start consumer. 01:19.980 --> 01:27.180 And let's basically start one more consumer in the same group, just U.S. command, Sidiq Afkham based 01:27.180 --> 01:27.690 command. 01:29.740 --> 01:34.570 And now in a new step, let's try to read the details about this specific group. 01:34.810 --> 01:36.730 It will be a group like this. 01:37.030 --> 01:44.290 Let me copy this comment and let's read details about this consumer group, Sidiq Afkham based. 01:46.980 --> 01:53.310 And now we see three different partitions in topic of two, and there are two different consumers here, 01:53.320 --> 01:58.860 you see two different ideas that were assigned to different partitions, partitions, zero and one were 01:58.860 --> 02:00.510 assigned to third, the consumer. 02:00.660 --> 02:04.510 And the last partition we decided to was assigned to second consumer. 02:05.100 --> 02:12.150 Now, while those consumers are listening, let's try to launch a performance producer and produce the 02:12.150 --> 02:14.000 SAMATHA just at specific rate. 02:14.400 --> 02:19.860 Let's go to our file here and let's scroll down to Caffe Coproducer Performance Test. 02:20.190 --> 02:28.140 And let's produce just, let's say, one thousand records at the rate of, let's say, ten records per 02:28.140 --> 02:35.670 second and let's increase record sales and let's make it equal to 100 kilobytes like this. 02:35.670 --> 02:38.630 And also, don't forget to adjust the topic name. 02:38.640 --> 02:44.340 We would like to produce no messages to pair of two topics that we have created just for purposes of 02:44.340 --> 02:45.250 the current lecture. 02:45.690 --> 02:47.350 So let me copy this. 02:47.430 --> 02:49.030 Come and go here. 02:49.050 --> 02:50.310 Open up new tab. 02:50.550 --> 02:51.660 KDDI took Afkham. 02:52.540 --> 02:59.110 And star performers producer, while it is running, let's go to our consumers and verify whether they 02:59.110 --> 03:01.210 are receiving messages and yes, they are. 03:01.600 --> 03:06.970 Now, let's go to the step where we can read details about specific consumer group and let's try to 03:07.390 --> 03:09.960 execute this command and see picture now. 03:10.120 --> 03:12.610 And now you should see here such numbers. 03:13.060 --> 03:19.120 And now here in this current of satcom, you'll see last committed of sales by consumers. 03:19.120 --> 03:24.010 And you'll see that in partition zero last committed offset is forty five. 03:24.160 --> 03:26.590 And it was committed by the consumer. 03:26.980 --> 03:32.130 Of course, since the execution of this comment, command numbers are where I was or around this command. 03:32.140 --> 03:35.380 And now we see that current offsets are following. 03:35.740 --> 03:42.910 For example, in Patison with ideato currently committed offset is two hundred thirty two and it was 03:42.910 --> 03:45.220 committed by consumers with this idea. 03:45.790 --> 03:53.260 But in look and offset, you see actual last offset numbers for every partyism. 03:53.470 --> 03:57.310 And at the moment Partition Zero has 210 messages. 03:57.520 --> 03:59.020 It is lost offset. 03:59.380 --> 04:03.850 And here you see the difference between this number and this number. 04:04.120 --> 04:06.510 And this difference is equal to three. 04:06.760 --> 04:08.710 And that's what lag means. 04:09.220 --> 04:15.010 This consumer has not yet consumed last three mass and just hit this partition. 04:15.440 --> 04:20.940 It wasn't able to consume them as quickly as they were arriving to this partition. 04:21.280 --> 04:24.280 That's why here you see Lieke in a previous output. 04:24.280 --> 04:30.250 You also see like numbers that were equal to 11 nine and allowing for different partitions. 04:31.030 --> 04:36.820 Let's try to rerun this command once again and noncurrent of sets and look. 04:36.820 --> 04:41.500 And offsets are equal and there are no less solek is zero. 04:41.740 --> 04:47.200 And that means that all consumers have successfully read the old messages in all partitions. 04:47.320 --> 04:53.500 In topic of two, if you want to, you could increase the numbers here in this performance producer 04:53.500 --> 04:56.310 and produce more messages at the higher rates. 04:56.500 --> 05:00.000 And you'll see here Hilex in this column. 05:00.280 --> 05:06.010 But my goal for this last year was to show you what it's like and the when it appears, it appears one 05:06.010 --> 05:10.440 consumer has not yet read all messages in specific partition. 05:10.930 --> 05:12.810 That's all for this lecture and the next. 05:12.820 --> 05:16.090 Let me quickly summarize what we have explored in this example. 05:16.240 --> 05:17.140 I'll see you next. 05:17.160 --> 05:17.640 Bye bye.