kafka二進制包：https://dlcdn.apache.org/kafka/3.7.0/kafka_2.13-3.7.0.tgz

集群規劃

主機名	IP地址	節點ID	角色分配
kafka1	192.168.100.100	1	broker,controller
kafka2	192.168.100.101	2	broker,controller
kafka3	192.168.100.102	3	broker,controller

編輯配置文件

config/kraft/server.properties

# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#    http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.#
# This configuration file is intended for use in KRaft mode, where
# Apache ZooKeeper is not present.  See config/kraft/README.md for details.
############################## Server Basics ############################## The role of this server. Setting this puts us in KRaft mode
# 標識該節點所承擔的角色，在KRaft模式下需要設置這個值
process.roles=broker,controller# The node id associated with this instance's roles
# 節點的ID，和節點所承擔的角色相關聯，唯一 每個服務器不一樣
node.id=1# The connect string for the controller quorum
# controller quorum 連接的集群地址字符串。和配置zk連接差不多，只是格式不一樣 每個服務器一樣
controller.quorum.voters=1@192.168.100.100:9093,2@192.168.100.101:9093,3@192.168.100.102:9093############################# Socket Server Settings ############################## The address the socket server listens on. It will get the value returned from
# java.net.InetAddress.getCanonicalHostName() if not configured.
#   FORMAT:
#     listeners = listener_name://host_name:port
#   EXAMPLE:
#     listeners = PLAINTEXT://your.host.name:9092
## 本機ip+端口 每個服務器不一樣
listeners=PLAINTEXT://192.168.100.100:9092,CONTROLLER://192.168.100.100:9093
inter.broker.listener.name=PLAINTEXT# Hostname and port the broker will advertise to producers and consumers. If not set,
# it uses the value for "listeners" if configured.  Otherwise, it will use the value
# returned from java.net.InetAddress.getCanonicalHostName().
## 本機ip+端口 每個服務器不一樣
advertised.listeners=PLAINTEXT://192.168.100.100:9092# Listener, host name, and port for the controller to advertise to the brokers. If
# this server is a controller, this listener must be configured.
controller.listener.names=CONTROLLER# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
listener.security.protocol.map=CONTROLLER:PLAINTEXT,PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL# The number of threads that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=3# The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads=8# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=102400# The receive buffer (SO_RCVBUF) used by the socket server
socket.receive.buffer.bytes=102400# The maximum size of a request that the socket server will accept (protection against OOM)
socket.request.max.bytes=104857600############################# Log Basics ############################## A comma separated list of directories under which to store log files
# 數據日志目錄
log.dirs=/tmp/kraft-combined-logs# The default number of log partitions per topic. More partitions allow greater
# parallelism for consumption, but this will also result in more files across
# the brokers.
num.partitions=1# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
# This value is recommended to be increased for installations with data dirs located in RAID array.
num.recovery.threads.per.data.dir=1############################# Internal Topic Settings  #############################
# The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
# For anything other than development testing, a value greater than 1 is recommended to ensure availability such as 3.
offsets.topic.replication.factor=1
transaction.state.log.replication.factor=1
transaction.state.log.min.isr=1############################# Log Flush Policy ############################## Messages are immediately written to the filesystem but by default we only fsync() to sync
# the OS cache lazily. The following configurations control the flush of data to disk.
# There are a few important trade-offs here:
#    1. Durability: Unflushed data may be lost if you are not using replication.
#    2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush.
#    3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks.
# The settings below allow one to configure the flush policy to flush data after a period of time or
# every N messages (or both). This can be done globally and overridden on a per-topic basis.# The number of messages to accept before forcing a flush of data to disk
#log.flush.interval.messages=10000# The maximum amount of time a message can sit in a log before we force a flush
#log.flush.interval.ms=1000############################# Log Retention Policy ############################## The following configurations control the disposal of log segments. The policy can
# be set to delete segments after a period of time, or after a given size has accumulated.
# A segment will be deleted whenever *either* of these criteria are met. Deletion always happens
# from the end of the log.# The minimum age of a log file to be eligible for deletion due to age
log.retention.hours=168# A size-based retention policy for logs. Segments are pruned from the log unless the remaining
# segments drop below log.retention.bytes. Functions independently of log.retention.hours.
#log.retention.bytes=1073741824# The maximum size of a log segment file. When this size is reached a new log segment will be created.
log.segment.bytes=1073741824# The interval at which log segments are checked to see if they can be deleted according
# to the retention policies
log.retention.check.interval.ms=300000

process.roles :

• 如果process.roles = broker, 服務器在KRaft模式中充當 broker。
• 如果process.roles = controller, 服務器在KRaft模式下充當 controller。
• 如果process.roles = broker,controller，服務器在KRaft模式中同時充當 broker controller。
• 如果process.roles 沒有設置。那么集群就假定是運行在ZooKeeper模式下。

同時充當Broker和Controller的節點稱為“組合”節點。

controller.quorum.voters：

• 系統中的所有節點都必須設置 controller.quorum.voters 配置。
• 這個配置標識有哪些節點是 Quorum 的投票者節點。所有想成為控制器的節點都需要包含在這個配置里面。這類似于在使用ZooKeeper時，使用ZooKeeper.connect配置時必須包含所有的ZooKeeper服務器。
• 然而，與ZooKeeper配置不同的是，controller.quorum.voters 配置需要包含每個節點的id。格式為: id1@host1:port1,id2@host2:port2。

生成集群唯一ID

bin/kafka-storage.sh random-uuid

格式化存儲目錄

如果是單節點模式運行，你需要在機器上執行如下命令。 如果是多個節點，則應該在每個節點上都分別運行format命令，以便格式化每臺機器上的。請確保為每個集群使用相同的集群ID。

bin/kafka-storage.sh format -t [上面生成的ID] -c ./config/kraft/server.properties

啟動服務端

在每個節點上執行啟動命令

bin/kafka-server-start.sh ./config/kraft/server.properties 

?關閉服務端

bin/kafka-server-stop.sh stop

參考資料：https://juejin.cn/post/7030974149115772964