WEBVTT

00:04.290 --> 00:09.240
Let's now bring back a brokers and verify whether the show will be changed here or not.

00:09.480 --> 00:13.040
So let's go to broker with a desirable started over again.

00:13.990 --> 00:16.900
And let's do the same for Breuker with one.

00:22.970 --> 00:24.060
Ray, where I started.

00:24.260 --> 00:29.110
Let's go to topics here and read the tales about Topic Month once again.

00:31.200 --> 00:38.370
And I see that the broker with 82 is still a leader for all politicians, but in-sync replica information

00:38.370 --> 00:44.270
was changed and now you see here two remaining brokers, and that is temporal, actually.

00:44.280 --> 00:49.890
And in some time, this cluster will be rebalanced and the leaders will be around for different partitions

00:50.040 --> 00:51.630
to make it more balanced.

00:52.200 --> 00:55.140
Let me try to enter this comment once over.

00:56.040 --> 01:01.470
And yes, it seems that, no, Kloster was a rebalanced and now there are different leaders for different

01:01.480 --> 01:02.180
positions.

01:02.910 --> 01:07.940
That's the whole picture was changed after we were brought up again, brokers that were down.

01:08.460 --> 01:08.810
Great.

01:09.000 --> 01:15.510
Let's now go to consumer and try to launch it over again and see whether we will still get the old messages

01:15.510 --> 01:15.910
or not.

01:16.110 --> 01:21.030
So let's go to our comment that will read all messages from topic month from beginning after.

01:22.460 --> 01:29.690
And I still see an entire list of all messages and no warnings at all, and situation is not back to

01:29.690 --> 01:30.160
normal.

01:30.560 --> 01:36.730
That's what happens when you bring down or bring up, again, different brokers in the Gloucester where

01:36.740 --> 01:39.040
topics have replication configured.

01:39.050 --> 01:45.170
And if replication is in place, nothing will change in terms of consumption and the production of messages.

01:45.290 --> 01:49.080
And the North Inglaterra will be lost and we won't be able to be read.

01:49.460 --> 01:50.240
So that's all.

01:50.240 --> 01:50.950
And next.

01:50.990 --> 01:55.710
Let's quickly make a short summary of what we have explored here in this example.

01:55.850 --> 01:56.700
I'll see you next.

01:56.720 --> 01:57.160
Bye bye.