kafka with others

Ethereal Lv4

1. 部署kafka

1.1 下载

1
2
3
4
yum install -y java
mkdir kafka && cd kafka
wget https://kafka.apache.org/downloads
tar xvf kafka_2.13-3.9.0.tgz

1.2 配置

1
2
cd kafka/kafka_2.13-3.9.0/config/kraft
vim server.properties
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
# 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.
#

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

# The role of this server. Setting this puts us in KRaft mode
process.roles=broker,controller

# The node id associated with this instance's roles
node.id=1

# The connect string for the controller quorum
controller.quorum.voters=1@10.9.98.111:9093,2@10.9.98.214:9093

############################# Socket Server Settings #############################

# The address the socket server listens on.
# Combined nodes (i.e. those with `process.roles=broker,controller`) must list the controller listener here at a minimum.
# If the broker listener is not defined, the default listener will use a host name that is equal to the value of java.net.InetAddress.getCanonicalHostName(),
# with PLAINTEXT listener name, and port 9092.
# FORMAT:
# listeners = listener_name://host_name:port
# EXAMPLE:
# listeners = PLAINTEXT://your.host.name:9092
listeners=PLAINTEXT://:9092,CONTROLLER://:9093

# Name of listener used for communication between brokers.
inter.broker.listener.name=PLAINTEXT

# Listener name, hostname and port the broker or the controller will advertise to clients.
# If not set, it uses the value for "listeners".
advertised.listeners=PLAINTEXT://10.9.98.111:9092,CONTROLLER://10.9.98.111:9093

# A comma-separated list of the names of the listeners used by the controller.
# If no explicit mapping set in `listener.security.protocol.map`, default will be using PLAINTEXT protocol
# This is required if running in KRaft mode.
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

其中注意:controller.quorum.voters需要配置所有节点,advertised.listeners配置自身

1.3 生成id并同步

1
2
bin/kafka-storage.sh random-uuid
# 输出:AjJP7bgUTFOJLSh5oCwEyw
1
2
3
# 所有节点都需要执行:
bin/kafka-storage.sh format -t AjJP7bgUTFOJLSh5oCwEyw -c ./config/kraft/server.properties
# 输出:Formatting metadata directory /tmp/kraft-combined-logs with metadata.version 3.9-IV0.
1
2
3
# 启动
bin/kafka-server-start.sh /root/kafka/kafka_2.13-3.9.0/config/kraft/server.properties
# bin/kafka-server-start.sh -daemon /root/kafka/kafka_2.13-3.9.0/config/kraft/server.properties # 后台运行

2. 测试添加topic

2.1 随机添加topic

1
2
3
4
./kafka-topics.sh --bootstrap-server 10.9.98.111:9092,10.9.98.214:9092 --create --topic testtopic
./kafka-topics.sh --bootstrap-server 10.9.98.111:9092,10.9.98.214:9092 --describe --topic testtopic
Topic: testtopic TopicId: qQCmedACRju8DaI-mV2hdg PartitionCount: 1 ReplicationFactor: 1 Configs: segment.bytes=1073741824
Topic: testtopic Partition: 0 Leader: 1 Replicas: 1 Isr: 1 Elr: LastKnownElr:

2.2 向指定broker添加topic

1
2
3
4
./kafka-topics.sh --bootstrap-server 10.9.98.111:9092,10.9.98.214:9092 --create --topic testtopic6 --replica-assignment 2
./kafka-topics.sh --bootstrap-server 10.9.98.111:9092,10.9.98.214:9092 --describe --topic testtopic6
Topic: testtopic6 TopicId: GxdlNgyLRzqr9ZgWmItJGw PartitionCount: 1 ReplicationFactor: 1 Configs: segment.bytes=1073741824
Topic: testtopic6 Partition: 0 Leader: 2 Replicas: 2 Isr: 2 Elr: LastKnownElr:

2.3 指定多个分区

1
2
3
4
5
6
./kafka-topics.sh --bootstrap-server 10.9.98.111:9092,10.9.98.214:9092   --create --topic testtopic5   --partitions 3  --replication-factor 1
./kafka-topics.sh --bootstrap-server 10.9.98.111:9092,10.9.98.214:9092 --describe --topic testtopic5
Topic: testtopic5 TopicId: bsBCmX5TQ1WaBRMXO_O5yQ PartitionCount: 3 ReplicationFactor: 1 Configs: segment.bytes=1073741824
Topic: testtopic5 Partition: 0 Leader: 2 Replicas: 2 Isr: 2 Elr: LastKnownElr:
Topic: testtopic5 Partition: 1 Leader: 1 Replicas: 1 Isr: 1 Elr: LastKnownElr:
Topic: testtopic5 Partition: 2 Leader: 2 Replicas: 2 Isr: 2 Elr: LastKnownElr:

2.4 指定多个备份

1
2
3
4
5
6
./kafka-topics.sh --bootstrap-server 10.9.98.111:9092,10.9.98.214:9092   --create --topic testtopic3   --partitions 3  --replication-factor 2
./kafka-topics.sh --bootstrap-server 10.9.98.111:9092,10.9.98.214:9092 --describe --topic testtopic3
Topic: testtopic3 TopicId: DKhBb4mfSe6Yl9ydV8uyVA PartitionCount: 3 ReplicationFactor: 2 Configs: segment.bytes=1073741824
Topic: testtopic3 Partition: 0 Leader: 2 Replicas: 2,1 Isr: 2,1 Elr: LastKnownElr:
Topic: testtopic3 Partition: 1 Leader: 1 Replicas: 1,2 Isr: 1,2 Elr: LastKnownElr:
Topic: testtopic3 Partition: 2 Leader: 1 Replicas: 1,2 Isr: 1,2 Elr: LastKnownElr:

3. 测试发送与订阅topic

3.1 发送与接受均多个Broker

1
2
3
4
5
6
./kafka-console-consumer.sh --bootstrap-server 10.9.98.111:9092,10.9.98.214:9092 --topic testtopic6
--from-beginning
123
123
lll
ll
1
2
3
./kafka-console-producer.sh --broker-list 10.9.98.111:9092,10.9.98.214:9092 --topic testtopic6
>123
>lll

3.2 发送单个broker,接受多个broker

1
2
3
4
5
6
7
./kafka-console-consumer.sh --bootstrap-server 10.9.98.111:9092,10.9.98.214:9092 --topic testtopic6
--from-beginning
123
123
lll
lll
aaa
1
2
3
./kafka-console-producer.sh --broker-list 10.9.98.214:9092 --topic testtopic6
>lll
>aaa

3.3 发送多个broker,接受单个broker

1
2
3
4
5
6
7
8
9
10
11
./kafka-console-consumer.sh --bootstrap-server 10.9.98.214:9092 --topic testtopic6 --from-beginning
123
123
lll
lll
aaa
ccc
mmm
ttt
cross
multiproducer
1
2
3
./kafka-console-producer.sh --broker-list 10.9.98.111:9092,10.9.98.214:9092 --topic testtopic6
>multiproducer
>ll

3.4 发送接受均为单个broker

1
2
3
4
5
6
7
8
9
./kafka-console-consumer.sh --bootstrap-server 10.9.98.111:9092 --topic testtopic6 --from-beginning
123
123
lll
lll
aaa
ccc
mmm
ttt
1
2
3
./kafka-console-producer.sh --broker-list 10.9.98.111:9092 --topic testtopic6
>mmm
>ttt

3.5 发送与接受Broker交叉

1
2
3
4
5
6
7
8
9
10
./kafka-console-consumer.sh --bootstrap-server 10.9.98.214:9092 --topic testtopic6 --from-beginning
123
123
lll
lll
aaa
ccc
mmm
ttt
cross
1
2
3
4
5
./kafka-console-producer.sh --broker-list 10.9.98.111:9092 --topic testtopic6
>mmm
>ttt
>cross
>

4. 参考

Kafka 3.6.1 Kraft模式 集群安装与部署 - SpringCore - 博客园

Apache Kafka

Kafka参数zookeeper和bootstrap-server的区别 - Clotho_Lee - 博客园

【云原生】一文搞懂Kafka中的listeners和advertised.listeners以及其他通信配置-腾讯云开发者社区-腾讯云

kafka连接两台机器使用以及python连接kafka的简单使用_kafka两台电脑发信息-CSDN博客

Kafka学习理解-listeners配置 - 孙行者、 - 博客园

  • Title: kafka with others
  • Author: Ethereal
  • Created at: 2025-02-07 17:46:28
  • Updated at: 2025-02-07 18:22:18
  • Link: https://ethereal-o.github.io/2025/02/07/kafka-with-others/
  • License: This work is licensed under CC BY-NC-SA 4.0.
 Comments