How to Monitor Apache Kafka

A message broker is a software that acts as an intermediary for sending messages between different applications. It functions like a server that receives messages from one application (called the producer) and routes them to one or more other applications (called consumers). The main purpose of a message broker is to ensure robust and reliable communication between different systems without requiring these systems to always be available or directly connected. This allows applications to work asynchronously, providing fault tolerance and the ability to operate in real time. A message broker can accept messages from multiple sources and efficiently route them to the appropriate receiver. Depending on the required business logic, messages can be grouped into topics or queues. There are many different message brokers, each with its own features and advantages. In this article, we'll focus on Kafka. Apache Kafka is a fast and scalable message broker capable of handling millions of messages per second. It is particularly valued for its fault tolerance and ability to store data for extended periods. Originally developed by LinkedIn, Kafka is now the most popular open-source solution in the message broker space and is licensed by the Apache Software Foundation. It is widely used to build real-time data pipelines and streaming applications. Moving and processing data streams between systems or applications is a critical task, and Kafka excels in helping users handle data streams in real-time with minimal latency. As a distributed system, Kafka is divided across multiple servers, which can store and process data streams in parallel. This distribution allows Kafka to provide real-time data processing for many different sources, ensuring reliability and resilience against system failures. In this article, we will explore how to install and configure Kafka on Windows, Ubuntu, and macOS,  so that you can take full advantage of it for your projects.  System Requirements Apache Kafka is designed to maximize the efficiency of the hardware it runs on. However, there are some general recommendations to keep in mind when setting up a system to work with this broker: Processor (CPU): Kafka usually doesn't require a lot of processing power since most operations are performed using direct disk access (zero-copy). However, the number of CPU cores can impact throughput. Memory (RAM): Having at least 8GB of RAM is recommended, but the final amount will depend heavily on the data load and the number of parallel operations. Disk Space: Kafka efficiently uses the file system and direct disk writing. It is preferable to use an SSD with high read/write speeds. It's also recommended that a separate disk be used to isolate its operations from other processes. Network: Kafka actively uses the network for data transmission. A stable connection with high bandwidth is recommended. Operating System: Apache Kafka generally runs on Unix-like systems such as Linux, but it does not restrict users from choosing other operating systems. Java: Since Kafka is written in Java, you will need the Java Development Kit (JDK) version 8 or higher. While Linux gives Kafka a key advantage in performance and scalability, the broker works well on both Windows and macOS. We'll discuss the pros and cons of each solution a bit later, but for now, let's proceed with the installation. Installing and Configuring Kafka on Windows The process of Kafka installation on Windows is straightforward but requires some care. Here's a step-by-step guide: Download and Install Java Development Kit (JDK): Apache Kafka runs on Java, so the first step is to install the development tools if they are not already installed. You can download the JDK from Oracle's official website. After installation, verify its functionality by entering the following command in the command prompt (cmd): java -version Download Apache Kafka: You can download Apache Kafka for Windows from the project's official website (look for Binary downloads). It is recommended that you choose the latest stable version (at the time of writing, this is 3.7.0). However, the installation process does not vary significantly between versions, so you can apply this guide to other versions as well). Unpacking: After downloading the archive, unpack it and move it to a convenient location. After unpacking the distribution, you will see various folders such as: bin: This folder contains executable files used to start and manage the distributed messaging system. The /windows subfolder contains special versions of files intended for use on Windows OS. config: This folder contains Kafka configuration files, including zookeeper.properties and server.properties, which can be edited for more precise setup. libs: This folder contains all the libraries needed to run Kafka. logs: This folder contains work logs, which can be useful for troubleshooting issues and finding dependencies between components. site-docs: This folder contains documentation for the Kafka version you installed, which can be helpful for beginners. LICENSE and NOTICE: These files contain the license agreement and legal notices. Basic Configuration of Data and Logging Directories: By default, log files and the data directory are saved in the /tmp folder, which can lead to performance, security, and data management issues. It is recommended to change the default paths to custom ones: Navigate to /config/server.properties and open the file in any text editor (e.g., VSCode). Find the log.dirs field (you can use the search function by pressing Ctrl+F). Change the default path /tmp/kafka-logs to a permanent path, e.g., c:/kafka/kafka-logs. Save the file and close it. Perform similar actions for the data directory: Navigate to /config/zookeeper.properties and open the file in any text editor. In the dataDir parameter, change the default path to a custom one. An example of a permanent path is shown in the screenshot below. The basic setup is now complete. This is enough to start the Zookeeper and Kafka servers and verify that the system is working. Starting Zookeeper and Kafka Servers: To start, navigate to the folder with the unpacked archive and open the command prompt. To start Zookeeper, use the following command: .\bin\windows\zookeeper-server-start.bat .\config\zookeeper.properties Note that our Zookeeper is running on port 2181, which is the default port for this service. If you encounter the error "The input line is too long. The syntax of the command is incorrect", move the Kafka folder closer to the disk's root. During the startup of zookeeper-server-start.bat, the CLASSPATH is called multiple times, leading to the overflow of the variable. The cmd.exe environment supports no more than 8191 characters. Open a new terminal window to start the Kafka server and use the following command: .\bin\windows\kafka-server-start.bat .\config\server.properties Verifying Functionality: To verify that everything is working, try creating a topic using the following command: .\bin\windows\kafka-topics.bat --create --bootstrap-server localhost:9092 --partitions 1 --replication-factor 1 --topic TestTopic Note that port 2181 matches the open port for Zookeeper. To visualize, create another topic called NewTopic. Now check what topics exist with the following command: .\bin\windows\kafka-topics.bat --list --bootstrap-server localhost:9092 You can interact with the topic in a new command prompt by creating and reading several messages. To do this, enter the following command in a new window: .\bin\windows\kafka-console-producer.bat --broker-list localhost:9092 --topic TestTopic After the command starts, you can send any messages. To start receiving messages, enter the following command in a new console window: .\bin\windows\kafka-console-consumer.bat --bootstrap-server localhost:9092 --topic TestTopic --from-beginning As shown in the screenshot, we received messages on the TestTopic. This is a simple functionality that helps you understand and familiarize yourself with Kafka tools. However, things may go wrong during installation and testing. Here are some common issues that may arise: JDK Issues: Ensure you have installed the JDK, not just the JRE. Also, make sure the version is 8 or higher. Environment Variable Check: After installing Java, ensure that the JAVA_HOME variable is set correctly and that the path to the bin directory is included in the system path. Firewall and Antivirus Issues: Sometimes, third-party antivirus programs or firewalls can block Kafka. If you encounter connection issues, try disabling them temporarily. Ports: By default, Zookeeper listens on port 2181, and Kafka on 9092. Make sure these ports are free, or reassign the default ports for these services. Starting Zookeeper Before Kafka: Before starting Kafka, make sure Zookeeper is already running. If not, start Zookeeper. Improper Kafka Shutdown: If Kafka shuts down improperly, some data may still be left in the temporary folder. If you start encountering difficulties during startup, try clearing the temporary files. Installing and Configuring Kafka on Ubuntu The steps for installing Kafka on Ubuntu are quite similar to those for other Linux distributions. The main differences lie in each operating system's package managers and minor specifics. These steps also resemble the installation process for Windows, so you can refer to that section even if you're using Linux. Downloading and Installing the Java Development Kit (JDK) As mentioned earlier, Apache Kafka runs on Java, so the first step is to install the JDK. However, before doing so, it's recommended to update your package list and upgrade the package versions with the following commands: sudo apt updatesudo apt upgrade In Linux systems, the installation can be easily done via the terminal by entering the following commands: sudo apt install default-jresudo apt install default-jdk Downloading and Extracting Kafka You can download Apache Kafka from the official website. Select the latest stable version of the product. Use the wget utility from the console to download it: wget https://downloads.apache.org/kafka/3.7.0/kafka_2.13-3.7.0.tgz To extract the downloaded file, use this command: tar xzf kafka_2.13-3.7.0.tgz Note that the version of Kafka might be different when you read this, so the command, particularly the numbers in the link, might look different. After the above steps, you should have a folder with the product next to the archive. Navigate to this folder using: cd kafka_2.13-3.7.0 Verifying Functionality The remaining steps are similar to what was done for Windows, so it's recommended to read the instructions starting from the third point in that section. To start Zookeeper, enter the following command: bin/zookeeper-server-start.sh config/zookeeper.properties Then, in a new terminal window, start Kafka: bin/kafka-server-start.sh config/server.properties This covers the basic installation and configuration. You can configure various parameters for production environments such as multiple backups, network configuration, data partitioning, and more, but this process is more labor-intensive and complex. Common Issues with Kafka Installation on Ubuntu and other Linux distributions Permission Issues: Sometimes, permission problems arise in Linux when accessing certain files or directories. To bypass this, you can use sudo before commands that cause issues. However, be cautious as sudo gives full admin access, which might lead to security issues. Java Memory Errors: If you encounter Java memory problems while working with Kafka, try increasing the maximum memory allocated for the JVM using the -Xmx flag. You'll need to add this flag to the configuration file in /bin/kafka-server-start.sh. However, ensure that you leave enough memory for other processes on the system. Increasing the maximum JVM memory can slow down the system if JVM starts using all available resources. Version Management: Version issues can arise when working with Linux. Always check the version of Kafka and all related tools, such as Zookeeper, to ensure compatibility. Proper Shutdown of Kafka and Zookeeper: To shut down Kafka and Zookeeper on Linux, you can use the following commands: kafka-server-stop.shzookeeper-server-stop.sh It's recommended that these services are always stopped properly to avoid data loss. Logging Issues: Kafka generates a large number of logs. Ensure you have enough disk space and that log rotation is enabled. Port and File Limits: Make sure you have permission to open the necessary number of files or sockets. Linux has system limits that can be adjusted if needed. Installing and Configuring Kafka on MacOS Homebrew is a package manager that simplifies software installation on MacOS. Homebrew doesn't require admin rights to install software, making it convenient and reducing security risks. If you don't have Homebrew installed, you can install it by entering the following command in the terminal: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" In this case, you will need Homebrew to install Kafka and its dependencies. Updating Homebrew If you already have Homebrew installed, it's a good idea to update it to the latest version with: brew update Installing the Java Development Kit (JDK) To install JDK, you can use the Homebrew we just installed. Enter the following command in the terminal: brew install openjdk Installing Kafka Install Kafka with the following command: brew install kafka Starting Kafka and Zookeeper First, start Zookeeper, then Kafka. Replace /usr/local/bin with the path to the executable files for Kafka and Zookeeper if they are located elsewhere: zookeeper-server-start /usr/local/etc/kafka/zookeeper.propertieskafka-server-start /usr/local/etc/kafka/server.properties For simplicity, we launched Zookeeper and Kafka in standalone mode on a local machine. To create a full-fledged distributed network on multiple machines, adjust the configuration files accordingly. Key parameters to modify include: Partitions: These allow parallel data processing. The number of partitions determines how many streams can process data simultaneously within a topic. Replicas: Copies of existing partitions ensure fault tolerance. The number of replicas determines how many copies of each partition will be stored in the cluster. Broker Information: A complete list of all servers that will participate in the cluster. Common Issues When Installing Kafka on MacOS JDK Version: Ensure that JDK version 8 or higher is installed. If not, you might encounter an error when trying to launch Kafka. Environment Variables: Kafka may not work if environment variables are incorrectly set or not set at all. For instance, you must set the KAFKA_HOME environment variable to the directory path. Other environment variables like JAVA_HOME might also be necessary for proper operation. File Paths and Permissions: Kafka might not find the necessary files or fail to start if it doesn't have read and write permissions for certain directories. You might need to change permissions or move some files. Homebrew Issues: Ensure Homebrew is correctly installed and updated to the latest version. Sometimes, installation via Homebrew can lead to version conflicts or dependency issues. Dependency Issues: The system requires Zookeeper to function. Always start Zookeeper before Kafka. Ports: Kafka and Zookeeper use specific ports (9092 and 2181, respectively) by default. If other applications use these ports, Kafka won't be able to start. Configuration: Errors in Kafka configuration files or incorrectly set parameters can cause issues when attempting to start Kafka. Installing and Configuring Kafka in Docker Docker is a platform for developing, delivering, and running applications in containers. Containers allow you to package an application with all its environment and dependencies into a single package that can be easily distributed and installed on any system. Installing Kafka in Docker is a great way to quickly and easily start working with the system. Here are some simple steps for installation: Install Docker Download Docker from the official website in a way that suits your OS. Run an Instance Use this command to start a Kafka instance: docker run -p 9092:9092 apache/kafka:3.7.0 Note that your Kafka version may differ from the one in the example. You can verify the functionality of Kafka in a manner similar to the Linux installation section. Choosing an OS for Deploying Kafka As we've established, Kafka can be installed on all major operating systems, as well as in Docker. Depending on the specific situation and needs, each option has its own advantages and disadvantages. If you're deciding which OS to use for deploying Kafka, here are the pros and cons of each system: Windows Pros: Ease of Use: Windows remains one of the most popular operating systems with extensive documentation and community support. Integration: It integrates very well with other Microsoft products and services. Cons: Windows is not always the best choice for deploying server applications; you will likely encounter compatibility and performance issues. While PowerShell and WSL (Windows Subsystem for Linux) can simplify operations, these systems may not always be optimal for working with Linux applications. Kafka and Zookeeper are usually tested and used on Unix-like systems, which might lead to more bugs and issues. macOS Pros: Simple Installation: Installation is straightforward with minimal difficulties. User-Friendly Tools: Convenient tools for installing and managing software. Unix-Based System: Makes it easier to work with most tools. Cons: Resource-Intensive: If your Mac lacks sufficient resources, it may slow down operations. Compatibility Issues: Possible compatibility issues between macOS versions and Kafka could lead to critical errors. Linux Pros: Open Source Support: Since Linux is open-source and supported by a large community, there are almost always ways to solve any problem. Efficient Resource Use: Linux consumes fewer system resources, making it more efficient for running Kafka. Preferred for Server Applications: Linux-based operating systems are often the preferred choice for server applications. Cons: Technical Skills Required: More technical skills are needed for setup and management compared to Windows and macOS. GUI Installation Challenges: There may be difficulties when installing and configuring a GUI. Docker Pros: Portability: Docker containers can run on any operating system, simplifying broker deployment in various environments. Isolation: Docker provides isolation between applications, meaning Kafka's operation won't affect other applications. Reproducibility: Docker allows you to create configurations that are easy to replicate, simplifying updates and deployments. Integration with Other Tools: Docker interacts well with popular solutions, simplifying Kafka container management and scaling. Cons: Complexity: Docker adds an extra layer of complexity to the broker installation. Data Management: The broker stores all messages on disk, and managing this in a containerized environment can be challenging. Performance: As with any containerized system, the broker's performance may be limited by the container's resources, requiring fine-tuning of Docker. Management: Managing and monitoring a broker in a container can be complex, especially in large systems. You may need automation tools like Kubernetes and Prometheus. Overall, Linux is the most common choice for working with Apache Kafka, especially for servers and workstations. However, the choice of operating system will depend directly on your preferences and requirements. Running Kafka in the Cloud We've covered the process of installing Kafka on different operating systems, but this process can be time-consuming due to potential errors. If you want to avoid the hassle of installation and configuration, consider our solution. Hostman offers a flexible and scalable cloud solution for launching a Kafka instance in just a few minutes. You don't need to install or configure any software; just select a region and configuration. Hostman ensures stability and performance for your Kafka project, thanks to professional support and high-performance infrastructure. This allows you to fully focus on developing and scaling your project without worrying about the technical side of things. Try Hostman today and discover the benefits of working with reliable and high-performance cloud hosting server. Conclusion In this guide, we have covered how to install Kafka on Ubuntu, Windows, and other operating systems. Apache Kafka is a robust, reliable, and scalable message broker that offers high throughput, fault tolerance, and low latency. Here are some reasons why Kafka is a great choice for a messaging environment: High Throughput: Apache Kafka can handle millions of messages per second, making it an excellent choice for applications that process large volumes of real-time data. Fault Tolerance: Kafka provides recovery from failures and ensures high data availability through its replication mechanisms. Scalability: Kafka can easily scale by adding more nodes to the cluster without disrupting the service. Long-Term Data Storage: Unlike most other message brokers, Kafka supports long-term data storage. You can configure the retention period in Kafka, and the data will be stored until it expires. Distributed System: Kafka is inherently a distributed system, meaning messages can be consumed in any order and across multiple channels. Integration with Multiple Systems: Kafka can be easily integrated with various systems, such as Hadoop, Spark, Storm, Flink, and many others. Fast Processing: Apache Kafka provides low latency, making it an excellent choice for applications requiring real-time data processing. Publish-Subscribe Topology: Kafka allows data sources to send messages to topics, and recipient applications to subscribe to topics of interest. All these advantages make Kafka one of the most popular and reliable message brokers on the market.

Apache Kafka is a distributed streaming platform designed for building real-time data pipelines and applications. It provides a scalable, fault-tolerant infrastructure to handle streams of data across various applications. It excels in handling high-throughput, fault-tolerant, and publish-subscribe messaging, making it a popular choice for developers looking to implement real-time analytics and event-driven systems. This is a step-by-step guide to learn how to install Apache Kafka on Ubuntu 22.04. Prerequisites A cloud server with Ubuntu 22.04 installed A non-root user with sudo privileges At least 4GB of RAM. Step 1: Creating a user for Kafka The first step is to create a dedicated user to ensure that Kafka's operations do not interfere with the system's other functionalities. Add a new user called kafka: sudo adduser kafka Next, you need to add the kafka user to the sudo group to have the necessary privileges for Kafka installation. sudo adduser kafka sudo Then, log in to the kafka account: su -l kafka The kafka user now is ready to be used. Step 2: Installing Java Development Kit (JDK) Apache Kafka is written in Java and Scala, which means Java Runtime Environment (JRE) is required to run it. However, for a complete development setup that may involve custom Kafka clients or plugins, the full Java Development Kit (JDK) is recommended.  Installing Java Development Kit Open the terminal and update the package index: sudo apt update Install the OpenJDK 11 package: sudo apt install openjdk-11-jdk Now that you’ve installed the JDK, you can start downloading Kafka. Step 3: Downloading Kafka You can download the 3.4 Kafka version from here and extract it in a folder. Start by creating a folder named downloads to store the archive: mkdir ~/downloadscd ~/downloadswget https://archive.apache.org/dist/kafka/3.4.0/kafka_2.12-3.4.0.tgz Then, move to ~ and extract the archive you downloaded: cd ~tar -xvzf ~/downloads/kafka_2.12-3.4.0.tgz Let’s rename the directory kafka_2.12-3.4.0 to kafka. mv kafka_2.12-3.4.0/ kafka/ Now that you’ve downloaded Kafka, you can start configuring your Kafka server. Step 4: Configuring the Kafka server First, start by setting the log.dirs property to change the directory where the Kafka logs are. To do so, you need to edit the server.properties file: nano ~/kafka/config/server.properties Look for log.dirs and set the value to /home/kafka/kafka-logs. You can also change the value of num.partition to 3 so that when you create the topic you don’t specify the number of partitions, it will be 3 by default. Now that you’ve finished configuring your Kafka server, you can run the server. Step 5: Starting the Kafka server To start the Kafka server, you need to first start Zookeeper and then start Kafka. What is Zookeeper? Apache ZooKeeper manages coordination and configuration for distributed systems, such as Kafka. Kafka uses ZooKeeper to maintain the state between nodes in the Kafka cluster and to keep track of topics, partitions, and configurations.  In this release of Kafka, zookeeper comes with Kafka, so no need to install it.  To start Zookeeper & Kafka, there are 2 commands: ~/bin/zookeeper-server-start.sh  ~/kafka/config/zookeeper.properties~/kafka/bin/kafka-server-start.sh  ~/kafka/config/server.properties But, to be more efficient, you need to create systemd unit files and use systemctl instead. Unit File for Zookeeper: sudo nano /etc/systemd/system/zookeeper.service [Unit] Description=Apache Zookeeper Service Requires=network.target After=network.target [Service] Type=simple User=kafka ExecStart=/home/kafka/kafka/bin/zookeeper-server-start.sh /home/kafka/kafka/config/zookeeper.properties ExecStop=/home/kafka/kafka/bin/zookeeper-server-stop.sh Restart=on-abnormal [Install] WantedBy=multi-user.target  Unit File for Kafka: sudo nano /etc/systemd/system/kafka.service [Unit] Description=Apache Kafka Service that requires zookeeper service Requires=zookeeper.service After=zookeeper.service [Service] Type=simple User=kafka ExecStart= /home/kafka/kafka/bin/kafka-server-start.sh /home/kafka/kafka/config/server.properties ExecStop=/home/kafka/kafka/bin/kafka-server-stop.sh Restart=on-abnormal [Install] WantedBy=multi-user.target Then, you can start the Kafka server: sudo systemctl start kafka Check the status: sudo systemctl status kafka Step 6: Testing the Kafka server You can check if the Kafka server is up with netcat. By default, Kafka server runs on 9092: nc -vz localhost 9092 You can also check logs: cat ~/kafka/logs/server.log It looks like it’s all good.  If your server is running successfully, try to create a topic: ~/kafka/bin/kafka-topics.sh --bootstrap-server localhost:9092 --create --topic firstTopic  Let’s check the topics’ list: ~/kafka/bin/kafka-topics.sh --list --bootstrap-server localhost:9092 You can produce messages to the topic: ~/kafka/bin/kafka-console-producer.sh --bootstrap-server localhost:9092 --topic firstTopic You can then read the messages: ~/kafka/bin/kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic firstTopic --from-beginning Step 7: Setting up Kafka in production (optional) When transitioning from a development setup to a production environment, it's crucial to consider deploying Apache Kafka as a part of a cluster rather than as a single instance. A Kafka cluster ensures better reliability, scalability, and fault tolerance. Running a cluster involves multiple Kafka servers (brokers) and, typically, several ZooKeeper instances to manage the cluster's state. Here’s an overview of the process for establishing a robust multi-node Kafka environment. Overview of Setting Up a Multi-Node Kafka Cluster Infrastructure Preparation Nodes: Prepare multiple servers (physical or virtual) with Ubuntu 22.04 installed, and at least three brokers for production environments to ensure fault tolerance. Each server act as a Kafka broker. Networking: Ensure all nodes can communicate with each other. Consistent Software Installation Install Java on all brokers. Install Kafka on each node following the same steps used above, ensuring consistency across all installations. ZooKeeper Setup Cluster Configuration: Although a single ZooKeeper instance can manage a small Kafka cluster, a ZooKeeper ensemble (cluster) is recommended for production. Typically, this consists of an odd number of servers (at least three) to avoid split-brain scenarios and to ensure high availability and failover capabilities. Configure each ZooKeeper node with a unique identifier and set up the ensemble so that each Kafka node knows how to connect to the ZooKeeper cluster. Kafka Configuration Unique Broker ID: Each Kafka broker must be assigned a unique ID (change “broker.id” in server.properties). Network Configuration: Configure server properties to include listeners and advertised listeners for broker communication.  Replication Factor: Set the appropriate replication factor in Kafka settings to ensure that copies of each partition are stored on multiple brokers. This replication is key to Kafka’s fault tolerance. Starting the Services Start the ZooKeeper ensemble first, ensuring all nodes in the ensemble are up and communicating. Launch the Kafka brokers across all nodes. Check the logs to ensure that each broker has joined the cluster and is functioning correctly. Step 8: Installing CMAK (optional) CMAK (Cluster Manager for Apache Kafka, previously known as Kafka Manager) is a web-based management tool for Apache Kafka clusters. It provides a user-friendly interface for monitoring cluster health and performance, managing topics, and configuring multiple Kafka clusters.  CMAK will simplify complex administrative tasks, making it easier for users to maintain and optimize their Kafka environments. To install CMAK, you need to install sbt which is a build tool for Scala projects like CMAK. echo "deb https://repo.scala-sbt.org/scalasbt/debian all main" | sudo tee /etc/apt/sources.list.d/sbt.list echo "deb https://repo.scala-sbt.org/scalasbt/debian /" | sudo tee -a /etc/apt/sources.list.d/sbt.list curl -sL "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x2EE0EA64E40A89B84B2DF73499E82A75642AC823" | sudo apt-key add sudo apt update sudo apt install sbt Then clone the latest version of CMAK: git clone https://github.com/yahoo/CMAK.gitcd CMAK Use sbt to build CMAK. sbt clean dist This command compiles the application and packages it into a zip file under the target/universal/ directory. Install unzip to be able to extract the file: sudo apt install unzip Once the build process is complete, extract the generated ZIP file: cd target/universal/ unzip cmak-VERSION.zip mv cmak-VERSION cmak Change VERSION to the one that you have. Now, we need to set the host and port of zookeeper correctly. Open ~CMAK/target/universal/cmak/conf/application.conf and change zkhosts properties. And to be able to run cmak, we need to set JAVA_OPTS variable: export JAVA_OPTS="-Dconfig.file=/home/kafka/CMAK/target/universal/cmak/conf/application.conf -Dhttp.port=9000" Then, move to ~/CMAK/target/universal/cmak directory and start CMAK: ./bin/cmak Go to your browser, enter the address: yourhost:9000, and make sure you have the right firewall rules to access to it. Then, add your cluster by adding your zookeeper host. Click Add Cluster: Then add your host: Now, your CMAK is ready, you can manage your brokers, topics, partitions, and much more. To learn more please refer to the documentation.