WEBVTT 00:04.480 --> 00:10.840 We have just brought down one of the girls in our class and we have seen that the consumer is able to 00:10.840 --> 00:13.330 consume all messages same as before. 00:13.660 --> 00:18.280 And that's thanks to replication that was configured on a topic level basics. 00:18.760 --> 00:23.890 And now this consumer even does not tell us that one of the broken glass is down. 00:24.070 --> 00:26.940 It was successfully able to consume all messages. 00:27.430 --> 00:31.910 If I wish to produce TAP, I will not see any warnings here as well. 00:31.930 --> 00:34.030 So producer is still up and running. 00:34.750 --> 00:39.520 Now let's try to bring down additional brolga broker with a zero. 00:39.550 --> 00:44.680 So now I have Breuker zero here, Broecker one here it is down now. 00:44.890 --> 00:48.490 And the broker is Editta here and the BlueSky. 00:48.490 --> 00:51.870 But this consumer still Iranian kiya in the step. 00:51.880 --> 00:55.020 And let's bring down Breuker with 80 zero. 00:55.030 --> 00:57.250 So go here and control. 00:57.250 --> 00:57.600 See. 01:02.850 --> 01:09.360 Shutdown of the broker with zero was completed and noticed that there were some actions happening here 01:09.360 --> 01:16.730 in a consumer step, and if I switch here, you'll see here warning's connection to not zero, couldn't 01:16.770 --> 01:19.830 be established, broker may not be available. 01:20.520 --> 01:23.060 And I see the same messages here. 01:23.550 --> 01:27.900 And that means that this consumer has detected a change in a Kafka Gloster. 01:28.020 --> 01:35.760 And now it knows that the broker with a zero is down, but it still is up and running and is able to 01:35.760 --> 01:38.460 consume additional messages less quickly. 01:38.460 --> 01:40.770 Actually produce one more message here. 01:40.770 --> 01:43.140 And let's again type here May. 01:44.630 --> 01:49.260 Go here to consumer and yes, mate was a received here, same as before. 01:49.430 --> 01:51.210 So consumer is still wrong. 01:51.680 --> 01:58.190 Let's now go to the step where we have red details about topic month and let's execute same command. 02:01.010 --> 02:09.020 And no, after broadcast with Idiz zero and one are down, we see that broker with Editta is now leader 02:09.020 --> 02:12.140 for all partitions, and that's fully correct. 02:12.470 --> 02:15.090 There are no other brokers available in the Gaza. 02:15.470 --> 02:20.690 That's why this single broker was selected as leader for all partitions. 02:21.170 --> 02:27.890 And now here in this column, In-Sync Replicas, we see that the broker decided to use the in-sync for 02:27.890 --> 02:29.000 every partition. 02:29.270 --> 02:35.840 All of the brokers are unavailable and therefore unsynchronized, wonderful. 02:35.990 --> 02:42.500 This whole picture was changed after we had brought down broker with a zero and only one broker stayed 02:42.500 --> 02:42.960 alive. 02:43.490 --> 02:50.390 Let's not try to stop this consumerism and let's start over again and verify whether we will receive 02:50.390 --> 02:51.740 old messages or not. 02:52.160 --> 02:53.360 So let's stop it. 02:54.260 --> 02:57.650 Clear terminal and wrote on it again from beginning. 02:59.910 --> 03:05.910 And I have got the same list of messages as before and in total here, I should see 13 messages and 03:05.910 --> 03:06.960 yes is correct. 03:07.380 --> 03:10.920 But also along with the messages, I see some warnings. 03:11.100 --> 03:12.960 Breuker may not be available. 03:13.200 --> 03:17.580 And I see those messages for broadcast with night 92. 03:17.730 --> 03:23.160 It's all or zero and nineteen ninety three is our broker with one. 03:23.310 --> 03:25.680 And I see several such warnings. 03:26.130 --> 03:31.770 But again, my idea here is that we are still able to read messages from our coffeecake last year, 03:31.950 --> 03:34.620 even if single broker stays alive. 03:35.100 --> 03:35.520 Great. 03:35.800 --> 03:41.880 Now let's try to bring back a Bors brokers and verify whether a picture will be back to normal or not. 03:42.060 --> 03:43.060 So let's do that next. 03:43.080 --> 03:43.520 Bye bye.