集群安装
kafka集依赖于zookeeer，所以安装kafka 集群时，先确保zookeeper集群已经安装启动，参考 https://www.jianshu.com/p/9a325551f02c
以kafka 3.1.0 版本为例
1 . 下载安装包： 地址 https://kafka.apache.org/downloads
2 . 解压安装包并进入解压后的目录：
[root@iZuf6g3hri8hvnuqng6id7Z kafka]# tar -zxvf kafka_2.12-3.1.0.tgz
[root@iZuf6g3hri8hvnuqng6id7Z kafka]# cd kafka_2.12-3.1.0
[root@iZuf6g3hri8hvnuqng6id7Z kafka_2.12-3.1.0]# ls
bin config libs LICENSE licenses NOTICE site-docs
- 进入config配置目录：修改配置文件 server.properties中的broker.id, log.dirs,zookeeper.connect
# server.properties 文件
############################# Server Basics #############################
# The id of the broker. This must be set to a unique integer for each broker.
# 集群中的每个kafka节点的id，全剧唯一
broker.id=1
############################# 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
# 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=/root/kafka/kafka_2.12-3.1.0/data
# 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
############################# 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 集群的地址， /kafka 指的对应kafka集群在zookeeper中的数据根路径(可以不设置)
zookeeper.connect=localhost:2181,localhost:2182,localhost:2183/kafka
# 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
- 启动节点
进入到kafka bin目录下， 启动如下指令
# -daemon 守护进程方式运行 ,../config/server.properties : 指定对应的配置文件
[root@iZuf6g3hri8hvnuqng6id7Z bin]# ./kafka-server-start.sh -daemon ../config/server.properties
- 按照如上的方式，在其他服务器上启动对应的若干个kafka 节点， 组成集群
操作指令
1. 主题相关命令
主题相关操作指令主要基于kafka bin 目录下的 kafka-topics.sh
| 主要参数 | 描述 |
|---|---|
| --bootstrap-server <String:server to connect to> | 连接的kafka的主机名和端口号 |
| --topic <String: topic> | 操作的topic名称 |
| --create | 创建主题 |
| --delete | 删除主题 |
| --alter | 修改主题 |
| --list | 查看所有主题 |
| --describe | 查看主题详细描述 |
| --partitions <Integer: # of partitions> | 设置分区数 |
| --replication-factor<Integer: replication factor> | 设置分区副本 |
| --config <String: name=value> | 更新系统的默认的配置 |
- . 创建topic
# 创建名为test， 分区个数为1个， 副本2 个的topic
kafka-topics.sh --bootstrap-server 127.0.0.1:9092 --topic test --create --partitions 1 --replication-factor 2
Created topic test.
- . 查看当前服务器所有的topic
kafka-topics.sh --bootstrap-server 127.0.0.1:9092 --list
test
- . 查看对应主题的详细信息
kafka-topics.sh --bootstrap-server 127.0.0.1:9092 --topic test --describe
Topic: test TopicId: MPY45pufQ_m-bW7h_cSULQ PartitionCount: 1 ReplicationFactor: 2 Configs: segment.bytes=1073741824
Topic: test Partition: 0 Leader: 2 Replicas: 2,1 Isr: 2,1
- . 修改主题
# 修改test 的分区数从1 变为2
./kafka-topics.sh --bootstrap-server 127.0.0.1:9092 --topic test --alter --partitions 2
# 查看test 主题的详细信息
./kafka-topics.sh --bootstrap-server 127.0.0.1:9092 --topic test --describe
Topic: test TopicId: MPY45pufQ_m-bW7h_cSULQ PartitionCount: 2 ReplicationFactor: 2 Configs: segment.bytes=1073741824
Topic: test Partition: 0 Leader: 2 Replicas: 2,1 Isr: 2,1
Topic: test Partition: 1 Leader: 1 Replicas: 1,2 Isr: 1,2
2. 生产,消费者
生产者操作指令主要基于kafka bin 目录下的 kafka-console-producer.sh
./kafka-console-producer.sh --bootstrap-server 127.0.0.1:9092 --topic test
消费者操作指令主要基于kafka bin 目录下的 kafka-console-producer.sh
# --from-beginning： 消费的数据偏移从最开始，说明从头开始消费全部数据，默认是从最新的偏移量开始消费
./kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9092 --topic test --from-beginning
网友评论