Kafka 2.8.0 集群搭建-Windows

一、背景

1. Kafka与 Zookeeper

Kafka 2.8.0版本之前，Kafka使用 ZooKeeper 来存储有关分区和代理的元数据，并选择一个代理作为Kafka控制器。Kafka集群依赖Zookeeper集群，需同时维护Zookeeper与Kafka集群。

Kafka 2.8.0版本之及之后，Kafka用自管理的Quorum代替ZooKeeper管理元数据，官方称这个为 "Kafka Raft metadata mode"，即KRaft mode，移除对Zookeeper的依赖。KRaft模式下无需维护Zookeeper集群。

2. 现状

   Kafka当前最新版本为 2.8.0，虽然可以使用KRaft模式，但官方不推荐在生成环境中使用！

3. 参考

Kafka 2.8.0 正式发布，与ZooKeeper正式分手！ - 知乎 (zhihu.com)

为什么Kafka在2.8版本中会“抛弃”Zookeeper - 知乎 (zhihu.com)

二、试验环境

1. 系统

Windows 10 20H2

2. Zookeepeer

zookeeper官网

apache-zookeeper-3.7.0-bin.tar.gz下载地址

3. Kafka

Kafka官网

kafka_2.12-2.8.0.tgz

三、Kafka集群搭建（zookeeper版）

1. 说明

   本次试验使用单机集群搭建，多机集群类似单机集群搭建。

2. zookeeper 集群搭建（单ip多进程）

   参考：Zookeeper集群搭建-Windows (juejin.cn)

   说明：

   zookeeper 集群中开启3个服务

   server.0=127.0.0.1:8880:7770		#监听：2180
   server.1=127.0.0.1:8881:7771		#监听：2181
   server.2=127.0.0.1:8882:7772		#监听：2182
   

3. Kafka集群搭建（单机版，3服务）

   解压 kafka_2.12-2.8.0.tgz 至任意盘。

将.\ kafka_2.12-2.8.0\config文件夹下的server.properties文件, 复制3个并分别改名为server1.properties，server2.properties，server3.properties。

对server1.properties修改。

重点项：

broker.id=0					#id 号，保证集群中唯一值
listeners=PLAINTEXT://127.0.0.1:9092			#kafka服务1，开启的监听端口号
num.network.threads=3		#broker处理消息的最大线程数，处理网络io
num.io.threads=8		#broker 处理磁盘io的线程数
log.retention.hours=168			#日志保留时间，单位为小时:h
log.dirs=D:\\software\\kafka\\kafka_2.12-2.8.0_0\\logs\\log1   #kafka服务1存放日志路径
zookeeper.connect=127.0.0.1:2180,127.0.0.1:2181,127.0.0.1:2182 #这里为zookeeper集群中的服务

全部：

# 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.

# see kafka.server.KafkaConfig for additional details and defaults

############################# Server Basics #############################

# The id of the broker. This must be set to a unique integer for each broker.
broker.id=0					#id 号，保证集群中唯一值

############################# 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
#listeners=PLAINTEXT://:9092
listeners=PLAINTEXT://127.0.0.1:9092			#kafka服务1，开启的监听端口号

# 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().
#advertised.listeners=PLAINTEXT://your.host.name:9092

# 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=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		#broker处理消息的最大线程数，处理网络io

# The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads=8		#broker 处理磁盘io的线程数

# 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=D:\\software\\kafka\\kafka_2.12-2.8.0_0\\logs\\log1   #kafka服务1存放日志路径

# 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			#日志保留时间，单位为小时:h

# 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

############################# Zookeeper #############################

# Zookeeper connection string (see zookeeper docs for details).
# This is a comma separated host:port pairs, each corresponding to a zk
# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
# You can also append an optional chroot string to the urls to specify the
# root directory for all kafka znodes.
#zookeeper.connect=localhost:2180
zookeeper.connect=127.0.0.1:2180,127.0.0.1:2181,127.0.0.1:2182 #这里为zookeeper集群中的服务

# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=18000


############################# Group Coordinator Settings #############################

# The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
# The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms.
# The default value for this is 3 seconds.
# We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
# However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup.
group.initial.rebalance.delay.ms=0

对server2.properties修改。

重点项：

broker.id=1					#id 号，保证集群中唯一值
listeners=PLAINTEXT://127.0.0.1:9093			#kafka服务1，开启的监听端口号
num.network.threads=3		#broker处理消息的最大线程数，处理网络io
num.io.threads=8		#broker 处理磁盘io的线程数
log.retention.hours=168			#日志保留时间，单位为小时:h
log.dirs=D:\\software\\kafka\\kafka_2.12-2.8.0_0\\logs\\log1   #kafka服务1存放日志路径
zookeeper.connect=127.0.0.1:2180,127.0.0.1:2181,127.0.0.1:2182 #这里为zookeeper集群中的服务

对server3.properties修改。

重点项：

broker.id=2					#id 号，保证集群中唯一值
listeners=PLAINTEXT://127.0.0.1:9094			#kafka服务1，开启的监听端口号
num.network.threads=3		#broker处理消息的最大线程数，处理网络io
num.io.threads=8		#broker 处理磁盘io的线程数
log.retention.hours=168			#日志保留时间，单位为小时:h
log.dirs=D:\\software\\kafka\\kafka_2.12-2.8.0_0\\logs\\log1   #kafka服务1存放日志路径
zookeeper.connect=127.0.0.1:2180,127.0.0.1:2181,127.0.0.1:2182 #这里为zookeeper集群中的服务

启动kafka，在./kafka_2.12-2.8.0_0路径下执行命令：

bin\windows\kafka-server-start.bat config\server1.properties
bin\windows\kafka-server-start.bat config\server2.properties
bin\windows\kafka-server-start.bat config\server3.properties

四、Kafka集群搭建（KRaft版本）

五、参考

1. Kafka环境变量配置

2. Kafka集群搭建windows版

3. Kafka常见错误解决方法

kafka使用常见报错及解决方法 - 简书 (jianshu.com)

这篇好文章是转载于：学新通技术网