kafka 安装_kafaka安装-CSDN博客

本文链接：https://blog.csdn.net/abcdu1/article/details/113657627

1.环境配置

这里安装 kafka 2.2.0 ,将安装在3个节点，需要提前在3个节点安装好jdk和zookeeper，参考。

2.安装kafka

(1)下载解压

http://kafka.apache.org/downloads

wget https://archive.apache.org/dist/kafka/2.2.0/kafka_2.12-2.2.0.tgz
tar -xzf kafka_2.12-2.2.0.tgz
cd kafka_2.12-2.2.0

(2)修改配置文件

cp config/server.properties config/kafka-server.properties
vim config/kafka-server.properties

（1）将 zookeeper.connect=localhost:2181 修改为：zookeeper.connect=192.168.111.129:2181,192.168.111.130:2181,192.168.111.131:2181

（192.168.111.129:2181,192.168.111.130:2181,192.168.111.131:2181 是3个节点 zookeeper 集群列表。）

（2）注意其他两个节点除了修改zookeeper.connect 还需要修改 broker.id ,必须保证每个节点的 broker.id 不同。

（3）修改 listeners=PLAINTEXT://192.168.111.129:9092 , 192.168.111.129为节点IP

修改完的配置文件为：

# 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

############################# 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://192.168.111.129:9092

# 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

# 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/kafka-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 for 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

############################# 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=192.168.111.129:2181,192.168.111.130:2181,192.168.111.131:2181

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


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

（3）启动服务

在3个节点分别启动kafka服务

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

也可以添加 -daemon 参数，后台启动

bin/kafka-server-start.sh -daemon config/kafka-server.properties &

3.测试

(1)创建topic

bin/kafka-topics.sh --create --bootstrap-server 192.168.111.129:9092 --replication-factor 3 --partitions 1 --topic my-replicated-topic

查看创建的topic

bin/kafka-topics.sh --list --bootstrap-server 192.168.111.129:9092

(2)发送消息

bin/kafka-console-producer.sh --broker-list 192.168.111.129:9092 --topic my-replicated-topic

(3)消费数据

在其他记得点消费数据

bin/kafka-console-consumer.sh --bootstrap-server 192.168.111.129:9092 --topic my-replicated-topic  --from-beginning

（4）查看队列信息

bin/kafka-topics.sh --describe --bootstrap-server 192.168.111.129:9092 --topic my-replicated-topic

可以看出该topic只有一个分区；分区0 的leader是节点2 ；分区0有三个副本，分别在节点，2，0，1上；活跃节点是2，0，1 ，

Here is an explanation of output. The first line gives a summary of all the partitions, each additional line gives information about one partition. Since we have only one partition for this topic there is only one line.

"leader" is the node responsible for all reads and writes for the given partition. Each node will be the leader for a randomly selected portion of the partitions.
"replicas" is the list of nodes that replicate the log for this partition regardless of whether they are the leader or even if they are currently alive.
"isr" is the set of "in-sync" replicas. This is the subset of the replicas list that is currently alive and caught-up to the leader.

关掉节点2 上面的kafka 服务，查看队列信息显示如下：

可以看出分区0的leader 变为 0；活跃节点是 0，1；因为节点2的kafka服务已经关闭。

安装测试完成！

(5)删除kafka 中的所有数据

停止kafka消费者和生产者客户端程序；

停止集群中各个节点的kafka服务的程序；

停止集群中各个节点的zookeeper服务的程序；

rm -rf /tmp/kafka-logs /tmp/zookeeper

/tmp/kafka-logs :为配置文件kafka-server.properties 中 log.dirs 参数的值；

/tmp/zookeeper :为配置文件zoo.cfg 中 dataDir 参数的值；

4.常见错误

错误1.

[2022-06-28 18:32:47,040] ERROR Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
306 kafka.zookeeper.ZooKeeperClientTimeoutException: Timed out waiting for connection while in state: CONNECTING

完整错误如下：

[2022-06-28 18:43:33,852] INFO Initiating client connection, connectString=192.168.*.*:2181,192.168.*.*:2181 sessionTimeout=6000 watcher=kafka.zookeeper.ZooKeeperClient$ZooKeeperClientWatcher$@4a22f9e2 (org.apache.zookeeper.ZooKeeper)
[2022-06-28 18:43:33,862] INFO [ZooKeeperClient] Waiting until connected. (kafka.zookeeper.ZooKeeperClient)
[2022-06-28 18:43:39,863] INFO [ZooKeeperClient] Closing. (kafka.zookeeper.ZooKeeperClient)
[2022-06-28 18:43:43,874] INFO Opening socket connection to server 192.168.*.*/192.168.*.*:2181. Will not attempt to authenticate using SASL (unknown error) (org.apache.zookeeper.ClientCnxn)
[2022-06-28 18:43:43,878] INFO Socket connection established to 192.168.*.*/192.168.*.*:2181, initiating session (org.apache.zookeeper.ClientCnxn)
[2022-06-28 18:43:43,884] INFO Session establishment complete on server 192.168.0.155/192.168.0.155:2181, sessionid = 0x20005ecbd240005, negotiated timeout = 6000 (org.apache.zookeeper.ClientCnxn)
[2022-06-28 18:43:43,888] INFO Session: 0x20005ecbd240005 closed (org.apache.zookeeper.ZooKeeper)
[2022-06-28 18:43:43,889] INFO EventThread shut down for session: 0x20005ecbd240005 (org.apache.zookeeper.ClientCnxn)
[2022-06-28 18:43:43,890] INFO [ZooKeeperClient] Closed. (kafka.zookeeper.ZooKeeperClient)
[2022-06-28 18:43:43,893] ERROR Fatal error during KafkaServer startup. Prepare to shutdown (kafka.server.KafkaServer)
kafka.zookeeper.ZooKeeperClientTimeoutException: Timed out waiting for connection while in state: CONNECTING
	at kafka.zookeeper.ZooKeeperClient.$anonfun$waitUntilConnected$3(ZooKeeperClient.scala:242)
	at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
	at kafka.utils.CoreUtils$.inLock(CoreUtils.scala:251)
	at kafka.zookeeper.ZooKeeperClient.waitUntilConnected(ZooKeeperClient.scala:238)
	at kafka.zookeeper.ZooKeeperClient.<init>(ZooKeeperClient.scala:96)
	at kafka.zk.KafkaZkClient$.apply(KafkaZkClient.scala:1825)
	at kafka.server.KafkaServer.createZkClient$1(KafkaServer.scala:361)
	at kafka.server.KafkaServer.initZkClient(KafkaServer.scala:385)
	at kafka.server.KafkaServer.startup(KafkaServer.scala:205)
	at kafka.server.KafkaServerStartable.startup(KafkaServerStartable.scala:38)
	at kafka.Kafka$.main(Kafka.scala:75)
	at kafka.Kafka.main(Kafka.scala)
[2022-06-28 18:43:43,896] INFO shutting down (kafka.server.KafkaServer)
[2022-06-28 18:43:43,901] INFO shut down completed (kafka.server.KafkaServer)
[2022-06-28 18:43:43,902] ERROR Exiting Kafka. (kafka.server.KafkaServerStartable)
[2022-06-28 18:43:43,904] INFO shutting down (kafka.server.KafkaServer)

原因：连接超时

解决：

（1）打开配置文件

 vim config/kafka-server.properties

（2）将 zookeeper.connection.timeout.ms=6000 时间增大

修改为：zookeeper.connection.timeout.ms=60000

（3）重新启动

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

错误2.

ERROR java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment.

[2022-06-29 10:26:40,006] ERROR [KafkaApi-2] Error when handling request: clientId=2, correlationId=0, api=UPDATE_METADATA, body={controller_id=2,controller_epoch=4,broker_epoch=30064771241,topic_states=[],live_brokers=[{id=2,end_points=[{port=9092,host=centos701v.jl.bjzt.qianxin-inc.cn,listener_name=PLAINTEXT,security_protocol_type=0}],rack=null},{id=1,end_points=[{port=9092,host=localhost,listener_name=PLAINTEXT,security_protocol_type=0}],rack=null}]} (kafka.server.KafkaApis)
java.lang.IllegalStateException: Epoch 30064771241 larger than current broker epoch 30064771222
at kafka.server.KafkaApis.isBrokerEpochStale(KafkaApis.scala:2414)
at kafka.server.KafkaApis.handleUpdateMetadataRequest(KafkaApis.scala:236)
at kafka.server.KafkaApis.handle(KafkaApis.scala:114)
at kafka.server.KafkaRequestHandler.run(KafkaRequestHandler.scala:69)
at java.lang.Thread.run(Thread.java:748)

描述：

使用命令 bin/kafka-topics.sh --list --bootstrap-server localhost:9092 查看创建的topic

报错：

ERROR java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment.

原因：

找不到节点机器，因为通过localhost 找不到broker节点

解决：

（1）修改配置文件 kafka-server.properties

vim config/kafka-server.properties

取消注释 #listeners=PLAINTEXT://:9092

改为如下，192.168.***.*** 为本机IP

listeners=PLAINTEXT://192.168.***.***:9092

（2）使用下面命令操作kafka集群，192.168.***.*** 为集群列表

 bin/kafka-topics.sh --list --bootstrap-server 192.168.***.***:9092

参考:

1.jdk，zookeeper配置

https://blog.csdn.net/abcdu1/article/details/113591746

2.kafka下载

http://kafka.apache.org/downloads

3.官网教程

http://kafka.apache.org/22/documentation.html#quickstart

4.常见问题1参考

kafka.zookeeper.ZooKeeperClientTimeoutException: Timed out waiting for connection while in state: CONNECTING - Stack Overflowhttps://stackoverflow.com/questions/63933799/kafka-zookeeper-zookeeperclienttimeoutexception-timed-out-waiting-for-connectio