No, we have to keep ourselves up and running, and it loosens at brought to one eight one this one,
and it accepts connection to any IP address of this localhost.
That's what this record means.
OK, now let's try to start to Kafka once again and please know that we need to keep zookeeper's server
up and running.
Let me make this window smaller health screen size like soul Moorgate here and open up new tab and let's
drag it here below this one and here in this tab.
But let's start Cafcass Sarah.
And we will start at the same as in one of the previous lectures.
Go to folder COFCO.
And let's type been Kafka there, Sarah.
This started out as EDG does a path to executable file, which starts Kafka Sarah.
And next, after the space, specify specific path to configuration file for Kafka, Cancellara.
And now we will use default configuration file located in configure and file.
Name is Sarah.
The properties you can you step in order to see all options.
Let's press start once again and this command will start a server with configuration file located here
in this file server, the properties.
OK, let's press enter.
And no, Cafcass Silver was successfully started and now it is up and running.
Let's now go to visuals, to the court and try to observe several logs.
Now, go here and go to logs and find a file called Saradha Blog.
And now let's scroll to the very end of this file.
You'll see a bunch of logs here.
Let me get this step, and at the end of this log file, you'll see my search in for Kafka, Sarah with
a zero started, and that means that now Kafka server is up and running and we are able to use it for
messages.
But let me now scroll up a bit and to show you all the meaningful messages, first one is here, Broecker
ID zero.
Every broker or Cafcass server has a unique ID and this ID must be unique across Kafka, Kloster and
the default ID is zero and this is basically specified in configuration file for Kafka.
Sarah.
Let me quickly go back to configuration file of Cafcass from this one server properties.
And if I scroll up here in this file, you'll find Broecker.
I'd parameter here and default one is zero.
And this way here in this Saradha file we see here, Broecker ID zero.
OK, we'll scroll up and find another line.
This one a wait and socket connections on this IP address and Dysport.
And that means that Kafka, Sara Kafka Breuker is waiting now for connections at Port nine zero nine
two.
And again, here you see four zeros and that means that it will accept connection to any IP address
of your computer.
OK, next message I wanted to show you.
Log directory slash Kafka logs not found create ID and this folder will be basically used for storage
of Kafka messages.
Regret that.
I have explained the difference between look for this one located in Kafka folder and this folder where
Kafka will store its messages.
So in this folder logs folder, Kafka stories, let's say system looks like several log file and in
this folder to be Kafka logs, that is a default one.
Kafka will store messages that will be sent by producers and consumed by consumers.
And no worries, please.
Will will examine the contents of this logs folder in the next lecture.
No, let me scroll up a bit again.
And here you'll see a bunch of parameters that were actually used for start of this Kafka Breuker and
those parameters, our default parameters.
Let's go up to the beginning of those configuration parameters and notice that here in the right section,
you're also able to scroll and you'll see basically small text and you are able to navigate more easily.
So we need to find the logs related to connection to zookeeper.
And those logs start basically here connecting to zookeeper on localhost two one eight one.
And now zookeeper is up and running.
And that's why Cafcass server initializes new solution to this address.
Localhost Collomb two one eight one Dysport is used by Zookeeper and below you'll see that zookeeper
connection session will be basically successful.
So here with this message zookeeper, our client Cafcass cerebral connected.
And that is an indication that the calf casadevall Kafka broker has successfully connected to Zookeeper
Celebra.
And this message above creating a new look file basically comes from zookeeper and same message we have
seen here in terminal as last message in Zookeeper Windle.
This one great new look, file, log, dot one.
And if you'll navigate to TMB Doorkeepers version two, you'll find this file, all that one here.
And that's basically all what I wanted to show you here in this log file.
And please notice that this file will contain also all previous logs.
For example, here are logs that were related to the Strutt unsuccessful start of Kafka.
Sara.
Well, Zookeeper wasn't available.
So if you want to clean this log, file up, you should simply delete it and recreated from scratch.
OK, no zookeeper celebra and the Cafcass set are up and running and we are able to start using them
and send some messages.
But before doing that, let's observe contents of the log directory that will be used for storage of
the messages, Bykofsky, etcetera.
See you next.
Bye bye.