![186ac25327942b0a8965c02ef38e5760.png](https://i-blog.csdnimg.cn/blog_migrate/d03e18dbad6919abea821f6ad7d79e32.jpeg)
以下内容来自拉勾课程学习拉勾教育 - 拉勾旗下教育平台
以下内容来自拉勾课程学习拉勾教育 - 拉勾旗下教育平台
以下内容来自拉勾课程学习拉勾教育 - 拉勾旗下教育平台
高吞吐消息中间件Kafka集群环境搭建(3台kafka,3台zookeeper)
一、集群搭建要求
1.搭建设计
![be90c2fc905cff1da517a3b0891de923.png](https://i-blog.csdnimg.cn/blog_migrate/c22aa54ee227fcb703aada2ab2a59491.jpeg)
2.分配六台Linux,用于安装拥有三个节点的Kafka集群和三个节点的Zookeeper
![aedac7448d8af93b3de25b8792c726f2.png](https://i-blog.csdnimg.cn/blog_migrate/c2336fbfb7493beec62121ec68dafc96.png)
二、准备工作
准备六台机器
![48b255119d3a2b9a08e297cb1f1b87be.png](https://i-blog.csdnimg.cn/blog_migrate/c0028a70f4f9ee0b9c78e41d20876abe.png)
1.分配三台Linux,用于安装拥有三个节点的Kafka集群
kafkaCluster20 (192.168.80.20)
kafkaCluster21 (192.168.80.21)
kafkaCluster22 (192.168.80.22)
![630b8afe26b6d93b9f07ec9fdff2a19e.png](https://i-blog.csdnimg.cn/blog_migrate/47c44b3b3f40d30272e1aa4a158b3dd8.jpeg)
2.分配三台Linux,用于安装拥有三个节点的zookeeper集群
zookeeperCluster10 (192.168.80.10)
zookeeperCluster11 (192.168.80.11)
zookeeperCluster12 (192.168.80.12)
![ba8292b7cd06c95c3dcc5758c78eec6f.png](https://i-blog.csdnimg.cn/blog_migrate/ce053e9a0f34b216bcf2d8bbf57d7c23.jpeg)
3.配置六台主机的/etc/hostname文件,配置主机名称
![57ae19fb8cd40093c6a968eeba818298.png](https://i-blog.csdnimg.cn/blog_migrate/e47b55b5ce3c7f50269cdee081bc77f0.jpeg)
4.配置六台主机的/etc/hosts配置,配置主机和ip地址的映射关系
192.168.80.10 zookeeperCluster10
192.168.80.11 zookeeperCluster11
192.168.80.12 zookeeperCluster12
192.168.80.20 kafkaCluster20
192.168.80.21 kafkaCluster21
192.168.80.22 kafkaCluster22
![254763f20a520bcdb4c52f7f8e30053d.png](https://i-blog.csdnimg.cn/blog_migrate/7f2c6094c02069cc45efe1463860b6e8.jpeg)
三、zookeeper集群搭建(先操作zookeeperCluster11节点)
3.1 Linux安装JDK,三台Linux都安装(zookeeper需要依赖jdk环境)
1. 上传JDK到 zookeeper节点中任一台(先操作zookeeperCluster11节点)
可以在XShell安装lrzsz实现文件上传到Linux服务器:
XShell安装lrzsz实现文件上传到Linux服务器_chuanchengdabing的博客-CSDN博客blog.csdn.net![bcd4f81bad409d53827a910fdb6d7d84.png](https://i-blog.csdnimg.cn/blog_migrate/65edf24349b7fdf055159b1b0cd3807c.jpeg)
![6ebf48edee96cf85464f7541645f3e91.png](https://i-blog.csdnimg.cn/blog_migrate/8bb67cd25a616fa947e7846b362ee600.jpeg)
上传成功
![7d94585b686b390b91e390e403ed0828.png](https://i-blog.csdnimg.cn/blog_migrate/c592a29ca632828080fcc6c176eb2037.png)
2. 安装JDK
#使用rpm安装JDK
rpm -ivh jdk-8u261-linux-x64.rpm
![56af584142c6298277c4e4dcbe05146a.png](https://i-blog.csdnimg.cn/blog_migrate/fcaefaf45a0a6b07cbd87ae2cb60cfd0.jpeg)
jdk默认的安装路径
/usr/java/jdk1.8.0_261-amd64
![aa8708b41a6d739e76d316d2d3394799.png](https://i-blog.csdnimg.cn/blog_migrate/a479c570f6eb86299e0cf51eeada41f5.jpeg)
3. 配置JAVA_HOME / 配置JDK环境变量
#编辑配置文件
vim /etc/profile
# 文件最后添加两行
export JAVA_HOME=/usr/java/jdk1.8.0_261-amd64
export PATH=$PATH:$JAVA_HOME/bin
# 退出vim
![e75aa26c3636414ac8a0b2a26d674007.png](https://i-blog.csdnimg.cn/blog_migrate/a4ab029d217a4f9c9a906117873a93d4.jpeg)
4. 刷新配置文件,查看JDK是否正确安装
source /etc/profile
java -version
![6ce7ec20a833c1b6b38b536cd436b449.png](https://i-blog.csdnimg.cn/blog_migrate/1c67156c78d9cc3eaf9029cbd28b389f.jpeg)
5. 在其他两台zookeeper节点上拷贝jdk(zookeeperCluster12和zookeeperCluster10)
scp -r /usr/java/jdk1.8.0_261-amd64/ zookeeperCluster12:/usr/java/jdk1.8.0_261-amd64/
scp -r /usr/java/jdk1.8.0_261-amd64/ zookeeperCluster10:/usr/java/jdk1.8.0_261-amd64/
![5373b93b317f989da52544e8b5c2e142.png](https://i-blog.csdnimg.cn/blog_migrate/2b49cb867252527c330d69b949af9419.png)
拷贝完成
![e60f15ce0470eda741ea6dd6ae668878.png](https://i-blog.csdnimg.cn/blog_migrate/24daaba6d0f7f3eff50d4b9f9a221a0a.jpeg)
参考上述节点,配置zookeeperCluster12和zookeeperCluster10节点上jdk的环境变量
![d90f6277e302a2c14b35d9fefb056568.png](https://i-blog.csdnimg.cn/blog_migrate/de7d446b6df8da54cc5a247d67be623c.jpeg)
3.2 Linux 安装Zookeeper,三台Linux都安装,以搭建Zookeeper集群(先操作zookeeperCluster11节点)
1. 使用工具lrzsz上传zookeeper-3.4.14.tar.gz到Linux
![1ccc742169558f24a4d556565ae3d3eb.png](https://i-blog.csdnimg.cn/blog_migrate/2a4884420035ad6f8350ac5567c874cc.jpeg)
![821d801ec1cf0ac93f41a52d6edcc832.png](https://i-blog.csdnimg.cn/blog_migrate/b44ceb8c157bbd10884dcdde0aea5792.png)
2. 解压zookeeper 到 /opt目录
tar -zxf zookeeper-3.4.14.tar.gz -C /opt
![6bba1c183c2c99aebb9d57ff0b5dbc2e.png](https://i-blog.csdnimg.cn/blog_migrate/c9f54fcb51bf401e43bbe0e533ce26ed.png)
3. 拷贝并配置zookeeper配置文件
cd /opt/zookeeper-3.4.14/conf
cp zoo_sample.cfg zoo.cfg
vim zoo.cfg
![2e77d1e3946c28dd75a5e98f537b4ae1.png](https://i-blog.csdnimg.cn/blog_migrate/98b8c82af35531df90609d3dad96ad5d.png)
# 具体配置参数
# 设置
dataDir=/var/dabing/zookeeper/data
# 添加
server.2=zookeeperCluster10:2881:3881
server.1=zookeeperCluster11:2881:3881
server.3=zookeeperCluster12:2881:3881
# 退出vim
![c23677c3ce901191b40ba2a1eebca9a6.png](https://i-blog.csdnimg.cn/blog_migrate/8a2cf7267d13eb3f7be6f1d2118bfacc.jpeg)
4. 创建zookeeper数据存储目录和myid文件,唯一标识zookeeper
mkdir -p /var/dabing/zookeeper/data
echo 1 > /var/dabing/zookeeper/data/myid
![948ad7081e98221ad00cedfcefc56b08.png](https://i-blog.csdnimg.cn/blog_migrate/b32586ed262e342d2f21c9de197c3628.png)
5. 配置环境变量
vim /etc/profile
# 添加
export ZOOKEEPER_PREFIX=/opt/zookeeper-3.4.14
export PATH=$PATH:$ZOOKEEPER_PREFIX/bin
export ZOO_LOG_DIR=/var/dabing/zookeeper/log
# 退出vim,让配置生效
source /etc/profile
![15684c1bcf5f68a581331b8d097222cd.png](https://i-blog.csdnimg.cn/blog_migrate/d2c6a22437deeb8011118ca01ccebb89.jpeg)
6. 将/opt/zookeeper-3.4.14拷贝到zookeeperCluster10,zookeeperCluster12
scp -r /opt/zookeeper-3.4.14/ zookeeperCluster10:/opt
scp -r /opt/zookeeper-3.4.14/ zookeeperCluster12:/opt
![c947db13cdd34ba2bb167c88b061c5fb.png](https://i-blog.csdnimg.cn/blog_migrate/763ee0add1588aa7cb6475e6488e9aea.jpeg)
7. zookeeperCluster10配置
# 配置环境变量
vim /etc/profile
# 在配置JDK环境变量基础上,添加内容
export ZOOKEEPER_PREFIX=/opt/zookeeper-3.4.14
export PATH=$PATH:$ZOOKEEPER_PREFIX/bin
export ZOO_LOG_DIR=/var/dabing/zookeeper/log
# 退出vim,让配置生效
source /etc/profile
![da4d56f0fd06f3fc1f5a77dcf6f5c7a9.png](https://i-blog.csdnimg.cn/blog_migrate/4faab4fa2357d7b4d9ea64a7a4554757.jpeg)
mkdir -p /var/dabing/zookeeper/data
echo 2 > /var/dabing/zookeeper/data/myid
![85b67cb3e711a3e6f6b613825baad0d7.png](https://i-blog.csdnimg.cn/blog_migrate/153e7b35048ee473d65992756b721764.png)
8. zookeeperCluster12配置
# 配置环境变量
vim /etc/profile
# 在配置JDK环境变量基础上,添加内容
export ZOOKEEPER_PREFIX=/opt/zookeeper-3.4.14
export PATH=$PATH:$ZOOKEEPER_PREFIX/bin
export ZOO_LOG_DIR=/var/dabing/zookeeper/log
# 退出vim,让配置生效
source /etc/profile
![7ad48f5e05115000759767aee7b2af91.png](https://i-blog.csdnimg.cn/blog_migrate/55c19e441a0ddf1e629fc3143cb6dda9.jpeg)
mkdir -p /var/dabing/zookeeper/data
echo 3 > /var/dabing/zookeeper/data/myid
![96c280951f931fc6eb214e7c1eb6d1d4.png](https://i-blog.csdnimg.cn/blog_migrate/3176d16acccbd919618cbe35d54378cb.png)
9. 启动zookeeper
# 在三台Linux上启动Zookeeper
[root@zookeeperCluster10~]# zkServer.sh start
[root@zookeeperCluster11~]# zkServer.sh start
[root@zookeeperCluster12~]# zkServer.sh start
![b932931ed8a0cf2ddce0cccb0b756a2d.png](https://i-blog.csdnimg.cn/blog_migrate/a9b591beafd27f73d337b5b15ec13eae.jpeg)
10. 在三台Linux上查看Zookeeper的状态
[root@zookeeperCluster11 opt]# zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper-3.4.14/bin/../conf/zoo.cfg
Mode: follower
[root@zookeeperCluster12 zookeeper-3.4.14]# zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper-3.4.14/bin/../conf/zoo.cfg
Mode: leader
[root@zookeeperCluster10 conf]# zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /opt/zookeeper-3.4.14/bin/../conf/zoo.cfg
Mode: follower
可以发现zookeeperCluster12 节点是leader节点
![f9fb3fd2eeea131ef744a2f3ba05f054.png](https://i-blog.csdnimg.cn/blog_migrate/6812a860864552f0fa669d9f743a5a18.jpeg)
四、kafka集群搭建(先操作kafkaCluster21节点)
4.1 在jkafka集群安装jdk
1. 从zookeeper集群中任意一个节点拷贝已经安装好的jdk到kafka集群中
![06e3139cc88b318f46c9fc1ad6f32502.png](https://i-blog.csdnimg.cn/blog_migrate/1368164a194d5cecbcd381064a0401d2.png)
![055640df7b36f137faf2cba1e523f276.png](https://i-blog.csdnimg.cn/blog_migrate/d145d31e7f07ea442e5b2809f73353d4.png)
’
2. 配置jdk环境变量
![55cf6fbed513d28e8a0fdb402ee913a8.png](https://i-blog.csdnimg.cn/blog_migrate/705aba1491a389af5ca8aa8cf5d25c7d.jpeg)
4.2 安装Kafka
1. 上传并解压Kafka到/opt
![66390b2357efccc723dd456ac8af023d.png](https://i-blog.csdnimg.cn/blog_migrate/e5a678098e16dcd63811b6561d475a79.jpeg)
![a27e8613e224a1821ced67c667219a85.png](https://i-blog.csdnimg.cn/blog_migrate/81f0f718ce81e2f4bca3954dae20515c.png)
2. 解压到/opt
tar -zxf kafka_2.12-1.0.2.tgz -C /opt
![5fb19a8435d208f0a053a866a0bfb866.png](https://i-blog.csdnimg.cn/blog_migrate/0794b0f3775a67ae9ca18e9f15355352.png)
3. 配置Kafka到环境变量
配置环境变量,三台kafka节点都要配置
vim /etc/profile
添加以下内容:
export KAFKA_HOME=/opt/kafka_2.12-1.0.2
export PATH=$PATH:$KAFKA_HOME/bin
让配置生效
source /etc/profile
![8e26b327e52264e588b05c3c4dff954b.png](https://i-blog.csdnimg.cn/blog_migrate/bfbf02c2177e9409d4876c3417c7683f.jpeg)
4. kafkaCluster21配置(其他使用默认配置)
vim /opt/kafka_2.12-1.0.2/config/server.properties
broker.id=0
listeners=PLAINTEXT://:9092 # 当前节点的所有端口将服务发布出去
advertised.listeners=PLAINTEXT://kafkaCluster21:9092 #存储到zk中,供生产者和消费者使用
log.dirs=/var/dabing/kafka/kafka-logs
zookeeper.connect=zookeeperCluster10:2181,zookeeperCluster11:2181,zookeeperCluster12:2181/myKafka
############################# 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://:9092
listeners=PLAINTEXT://:9092
#advertised.listeners=PLAINTEXT://your.host.name:9092
advertised.listeners=PLAINTEXT://kafkaCluster21:9092
############################# Log Basics #############################
# A comma seperated list of directories under which to store log files
log.dirs=/var/dabing/kafka/kafka-logs
############################# 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=zookeeperCluster10:2181,zookeeperCluster11:2181,zookeeperCluster12:2181/myKafka
5. 将kafkaCluster21上配置好的kafka拷贝到kafkaCluster20和kafkaCluster22上
scp -r /opt/kafka_2.12-1.0.2/ kafkaCluster20:/opt/kafka_2.12-1.0.2
scp -r /opt/kafka_2.12-1.0.2/ kafkaCluster22:/opt/kafka_2.12-1.0.2
![b3ea0e929ce15c4eb7d8843a4a435994.png](https://i-blog.csdnimg.cn/blog_migrate/a75088735673c4f47be5a9e1af901edd.jpeg)
![c8bb2f4c9d1c36f640d20aa829745a8a.png](https://i-blog.csdnimg.cn/blog_migrate/deae087d509123ed974df9900460796d.jpeg)
![903cb8ce87231dd1ce26c485a5e09e38.png](https://i-blog.csdnimg.cn/blog_migrate/88f072d35bcc487f677277e31f69c75e.jpeg)
6. 在kafkaCluster20和kafkaCluster22上配置kafka环境变量
![fe82570954db26be81b7a4d7e0847484.png](https://i-blog.csdnimg.cn/blog_migrate/2da49558dd6029fa19da3c19f7a461f2.jpeg)
7. kafkaCluster20修改配置文件
vim /opt/kafka_2.12-1.0.2/config/server.properties
broker.id=1
listeners=PLAINTEXT://:9092
advertised.listeners=PLAINTEXT://kafkaCluster20:9092
log.dirs=/var/dabing/kafka/kafka-logs
zookeeper.connect=zookeeperCluster10:2181,zookeeperCluster11:2181,zookeeperCluster12:2181/myKafka
[root@kafkaCluster20 kafka_2.12-1.0.2]# vi /opt/kafka_2.12-1.0.2/config/server.properties
############################# Server Basics #############################
broker.id=1
############################# Socket Server Settings #############################
listeners=PLAINTEXT://:9092
advertised.listeners=PLAINTEXT://kafkaCluster20:9092
############################# Log Basics #############################
log.dirs=/var/dabing/kafka/kafka-logs
############################# Zookeeper #############################
zookeeper.connect=zookeeperCluster10:2181,zookeeperCluster11:2181,zookeeperCluster12:2181/myKafka
8. kafkaCluster22配置
vim /opt/kafka_2.12-1.0.2/config/server.properties
broker.id=2
listeners=PLAINTEXT://:9092
advertised.listeners=PLAINTEXT://kafkaCluster22:9092
log.dirs=/var/dabing/kafka/kafka-logs
zookeeper.connect=node2:2181,node3:2181,node4:2181/myKafka
[root@kafkaCluster22 kafka_2.12-1.0.2]# vi /opt/kafka_2.12-1.0.2/config/server.properties
############################# Server Basics #############################
broker.id=2
listeners=PLAINTEXT://:9092
advertised.listeners=PLAINTEXT://kafkaCluster22:9092
############################# Log Basics #############################
log.dirs=/var/dabing/kafka/kafka-logs
############################# Zookeeper #############################
zookeeper.connect=zookeeperCluster10:2181,zookeeperCluster11:2181,zookeeperCluster12:2181/myKafka
9. 启动Kafka
[root@kafkaCluster20~]# kafka-server-start.sh /opt/kafka_2.12-1.0.2/config/server.properties
[root@kafkaCluster21~]# kafka-server-start.sh /opt/kafka_2.12-1.0.2/config/server.properties
[root@kafkaCluster22~]# kafka-server-start.sh /opt/kafka_2.12-1.0.2/config/server.properties
启动kafkaCluster21节点上的kafka:
[root@kafkaCluster21 softInstall]# kafka-server-start.sh /opt/kafka_2.12-1.0.2/config/server.properties
启动kafkaCluster22节点上的kafka:
[root@kafkaCluster22 kafka_2.12-1.0.2]# kafka-server-start.sh /opt/kafka_2.12-1.0.2/config/server.properties
[2020-11-12 06:59:46,812] INFO KafkaConfig values:
advertised.host.name = null
advertised.listeners = PLAINTEXT://kafkaCluster22:9092
advertised.port = null
alter.config.policy.class.name = null
authorizer.class.name =
auto.create.topics.enable = true
auto.leader.rebalance.enable = true
background.threads = 10
broker.id = 2
broker.id.generation.enable = true
broker.rack = null
compression.type = producer
connections.max.idle.ms = 600000
controlled.shutdown.enable = true
controlled.shutdown.max.retries = 3
controlled.shutdown.retry.backoff.ms = 5000
controller.socket.timeout.ms = 30000
create.topic.policy.class.name = null
default.replication.factor = 1
delete.records.purgatory.purge.interval.requests = 1
delete.topic.enable = true
fetch.purgatory.purge.interval.requests = 1000
group.initial.rebalance.delay.ms = 0
group.max.session.timeout.ms = 300000
group.min.session.timeout.ms = 6000
host.name =
inter.broker.listener.name = null
inter.broker.protocol.version = 1.0-IV0
leader.imbalance.check.interval.seconds = 300
leader.imbalance.per.broker.percentage = 10
listener.security.protocol.map = PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL
listeners = PLAINTEXT://:9092
log.cleaner.backoff.ms = 15000
log.cleaner.dedupe.buffer.size = 134217728
log.cleaner.delete.retention.ms = 86400000
log.cleaner.enable = true
log.cleaner.io.buffer.load.factor = 0.9
log.cleaner.io.buffer.size = 524288
log.cleaner.io.max.bytes.per.second = 1.7976931348623157E308
log.cleaner.min.cleanable.ratio = 0.5
log.cleaner.min.compaction.lag.ms = 0
log.cleaner.threads = 1
log.cleanup.policy = [delete]
log.dir = /tmp/kafka-logs
log.dirs = /var/dabing/kafka/kafka-logs
log.flush.interval.messages = 9223372036854775807
log.flush.interval.ms = null
log.flush.offset.checkpoint.interval.ms = 60000
log.flush.scheduler.interval.ms = 9223372036854775807
log.flush.start.offset.checkpoint.interval.ms = 60000
log.index.interval.bytes = 4096
log.index.size.max.bytes = 10485760
log.message.format.version = 1.0-IV0
log.message.timestamp.difference.max.ms = 9223372036854775807
log.message.timestamp.type = CreateTime
log.preallocate = false
log.retention.bytes = -1
log.retention.check.interval.ms = 300000
log.retention.hours = 168
log.retention.minutes = null
log.retention.ms = null
log.roll.hours = 168
log.roll.jitter.hours = 0
log.roll.jitter.ms = null
log.roll.ms = null
log.segment.bytes = 1073741824
log.segment.delete.delay.ms = 60000
max.connections.per.ip = 2147483647
max.connections.per.ip.overrides =
message.max.bytes = 1000012
metric.reporters = []
metrics.num.samples = 2
metrics.recording.level = INFO
metrics.sample.window.ms = 30000
min.insync.replicas = 1
num.io.threads = 8
num.network.threads = 3
num.partitions = 1
num.recovery.threads.per.data.dir = 1
num.replica.fetchers = 1
offset.metadata.max.bytes = 4096
offsets.commit.required.acks = -1
offsets.commit.timeout.ms = 5000
offsets.load.buffer.size = 5242880
offsets.retention.check.interval.ms = 600000
offsets.retention.minutes = 1440
offsets.topic.compression.codec = 0
offsets.topic.num.partitions = 50
offsets.topic.replication.factor = 1
offsets.topic.segment.bytes = 104857600
port = 9092
principal.builder.class = null
producer.purgatory.purge.interval.requests = 1000
queued.max.request.bytes = -1
queued.max.requests = 500
quota.consumer.default = 9223372036854775807
quota.producer.default = 9223372036854775807
quota.window.num = 11
quota.window.size.seconds = 1
replica.fetch.backoff.ms = 1000
replica.fetch.max.bytes = 1048576
replica.fetch.min.bytes = 1
replica.fetch.response.max.bytes = 10485760
replica.fetch.wait.max.ms = 500
replica.high.watermark.checkpoint.interval.ms = 5000
replica.lag.time.max.ms = 10000
replica.socket.receive.buffer.bytes = 65536
replica.socket.timeout.ms = 30000
replication.quota.window.num = 11
replication.quota.window.size.seconds = 1
request.timeout.ms = 30000
reserved.broker.max.id = 1000
sasl.enabled.mechanisms = [GSSAPI]
sasl.kerberos.kinit.cmd = /usr/bin/kinit
sasl.kerberos.min.time.before.relogin = 60000
sasl.kerberos.principal.to.local.rules = [DEFAULT]
sasl.kerberos.service.name = null
sasl.kerberos.ticket.renew.jitter = 0.05
sasl.kerberos.ticket.renew.window.factor = 0.8
sasl.mechanism.inter.broker.protocol = GSSAPI
security.inter.broker.protocol = PLAINTEXT
socket.receive.buffer.bytes = 102400
socket.request.max.bytes = 104857600
socket.send.buffer.bytes = 102400
ssl.cipher.suites = null
ssl.client.auth = none
ssl.enabled.protocols = [TLSv1.2, TLSv1.1, TLSv1]
ssl.endpoint.identification.algorithm = null
ssl.key.password = null
ssl.keymanager.algorithm = SunX509
ssl.keystore.location = null
ssl.keystore.password = null
ssl.keystore.type = JKS
ssl.protocol = TLS
ssl.provider = null
ssl.secure.random.implementation = null
ssl.trustmanager.algorithm = PKIX
ssl.truststore.location = null
ssl.truststore.password = null
ssl.truststore.type = JKS
transaction.abort.timed.out.transaction.cleanup.interval.ms = 60000
transaction.max.timeout.ms = 900000
transaction.remove.expired.transaction.cleanup.interval.ms = 3600000
transaction.state.log.load.buffer.size = 5242880
transaction.state.log.min.isr = 1
transaction.state.log.num.partitions = 50
transaction.state.log.replication.factor = 1
transaction.state.log.segment.bytes = 104857600
transactional.id.expiration.ms = 604800000
unclean.leader.election.enable = false
zookeeper.connect = zookeeperCluster10:2181,zookeeperCluster11:2181,zookeeperCluster12:2181/myKafka
zookeeper.connection.timeout.ms = 6000
zookeeper.session.timeout.ms = 6000
zookeeper.set.acl = false
zookeeper.sync.time.ms = 2000
(kafka.server.KafkaConfig)
[2020-11-12 06:59:47,192] INFO starting (kafka.server.KafkaServer)
[2020-11-12 06:59:47,195] INFO Connecting to zookeeper on zookeeperCluster10:2181,zookeeperCluster11:2181,zookeeperCluster12:2181/myKafka (kafka.server.KafkaServer)
[2020-11-12 06:59:47,247] INFO Client environment:zookeeper.version=3.4.10-39d3a4f269333c922ed3db283be479f9deacaa0f, built on 03/23/2017 10:13 GMT (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,247] INFO Client environment:host.name=kafkaCluster22 (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,247] INFO Client environment:java.version=1.8.0_261 (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,247] INFO Client environment:java.vendor=Oracle Corporation (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,248] INFO Client environment:java.home=/usr/java/jdk1.8.0_261-amd64/jre (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,248] INFO Client environment:java.class.path=:/opt/kafka_2.12-1.0.2/bin/../libs/aopalliance-repackaged-2.5.0-b32.jar:/opt/kafka_2.12-1.0.2/bin/../libs/argparse4j-0.7.0.jar:/opt/kafka_2.12-1.0.2/bin/../libs/commons-lang3-3.5.jar:/opt/kafka_2.12-1.0.2/bin/../libs/connect-api-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/connect-file-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/connect-json-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/connect-runtime-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/connect-transforms-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/guava-20.0.jar:/opt/kafka_2.12-1.0.2/bin/../libs/hk2-api-2.5.0-b32.jar:/opt/kafka_2.12-1.0.2/bin/../libs/hk2-locator-2.5.0-b32.jar:/opt/kafka_2.12-1.0.2/bin/../libs/hk2-utils-2.5.0-b32.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jackson-annotations-2.9.6.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jackson-core-2.9.6.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jackson-databind-2.9.6.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jackson-jaxrs-base-2.9.6.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jackson-jaxrs-json-provider-2.9.6.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jackson-module-jaxb-annotations-2.9.6.jar:/opt/kafka_2.12-1.0.2/bin/../libs/javassist-3.20.0-GA.jar:/opt/kafka_2.12-1.0.2/bin/../libs/javassist-3.21.0-GA.jar:/opt/kafka_2.12-1.0.2/bin/../libs/javax.annotation-api-1.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/javax.inject-1.jar:/opt/kafka_2.12-1.0.2/bin/../libs/javax.inject-2.5.0-b32.jar:/opt/kafka_2.12-1.0.2/bin/../libs/javax.servlet-api-3.1.0.jar:/opt/kafka_2.12-1.0.2/bin/../libs/javax.ws.rs-api-2.0.1.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jersey-client-2.25.1.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jersey-common-2.25.1.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jersey-container-servlet-2.25.1.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jersey-container-servlet-core-2.25.1.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jersey-guava-2.25.1.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jersey-media-jaxb-2.25.1.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jersey-server-2.25.1.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jetty-continuation-9.2.22.v20170606.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jetty-http-9.2.22.v20170606.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jetty-io-9.2.22.v20170606.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jetty-security-9.2.22.v20170606.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jetty-server-9.2.22.v20170606.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jetty-servlet-9.2.22.v20170606.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jetty-servlets-9.2.22.v20170606.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jetty-util-9.2.22.v20170606.jar:/opt/kafka_2.12-1.0.2/bin/../libs/jopt-simple-5.0.4.jar:/opt/kafka_2.12-1.0.2/bin/../libs/kafka_2.12-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/kafka_2.12-1.0.2-sources.jar:/opt/kafka_2.12-1.0.2/bin/../libs/kafka_2.12-1.0.2-test-sources.jar:/opt/kafka_2.12-1.0.2/bin/../libs/kafka-clients-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/kafka-log4j-appender-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/kafka-streams-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/kafka-streams-examples-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/kafka-tools-1.0.2.jar:/opt/kafka_2.12-1.0.2/bin/../libs/log4j-1.2.17.jar:/opt/kafka_2.12-1.0.2/bin/../libs/lz4-java-1.4.jar:/opt/kafka_2.12-1.0.2/bin/../libs/maven-artifact-3.5.0.jar:/opt/kafka_2.12-1.0.2/bin/../libs/metrics-core-2.2.0.jar:/opt/kafka_2.12-1.0.2/bin/../libs/osgi-resource-locator-1.0.1.jar:/opt/kafka_2.12-1.0.2/bin/../libs/plexus-utils-3.0.24.jar:/opt/kafka_2.12-1.0.2/bin/../libs/reflections-0.9.11.jar:/opt/kafka_2.12-1.0.2/bin/../libs/rocksdbjni-5.7.3.jar:/opt/kafka_2.12-1.0.2/bin/../libs/scala-library-2.12.4.jar:/opt/kafka_2.12-1.0.2/bin/../libs/slf4j-api-1.7.25.jar:/opt/kafka_2.12-1.0.2/bin/../libs/slf4j-log4j12-1.7.25.jar:/opt/kafka_2.12-1.0.2/bin/../libs/snappy-java-1.1.4.jar:/opt/kafka_2.12-1.0.2/bin/../libs/validation-api-1.1.0.Final.jar:/opt/kafka_2.12-1.0.2/bin/../libs/zkclient-0.10.jar:/opt/kafka_2.12-1.0.2/bin/../libs/zookeeper-3.4.10.jar (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,250] INFO Client environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,250] INFO Client environment:java.io.tmpdir=/tmp (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,251] INFO Client environment:java.compiler=<NA> (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,251] INFO Client environment:os.name=Linux (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,251] INFO Client environment:os.arch=amd64 (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,251] INFO Client environment:os.version=3.10.0-957.el7.x86_64 (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,251] INFO Client environment:user.name=root (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,251] INFO Client environment:user.home=/root (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,251] INFO Client environment:user.dir=/opt/kafka_2.12-1.0.2 (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,253] INFO Initiating client connection, connectString=zookeeperCluster10:2181,zookeeperCluster11:2181,zookeeperCluster12:2181 sessionTimeout=6000 watcher=org.I0Itec.zkclient.ZkClient@1b1473ab (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,303] INFO Starting ZkClient event thread. (org.I0Itec.zkclient.ZkEventThread)
[2020-11-12 06:59:47,323] INFO Opening socket connection to server zookeeperCluster11/192.168.80.11:2181. Will not attempt to authenticate using SASL (unknown error) (org.apache.zookeeper.ClientCnxn)
[2020-11-12 06:59:47,328] INFO Socket connection established to zookeeperCluster11/192.168.80.11:2181, initiating session (org.apache.zookeeper.ClientCnxn)
[2020-11-12 06:59:47,331] INFO Waiting for keeper state SyncConnected (org.I0Itec.zkclient.ZkClient)
[2020-11-12 06:59:47,347] INFO Session establishment complete on server zookeeperCluster11/192.168.80.11:2181, sessionid = 0x100009c182d0001, negotiated timeout = 6000 (org.apache.zookeeper.ClientCnxn)
[2020-11-12 06:59:47,372] INFO zookeeper state changed (SyncConnected) (org.I0Itec.zkclient.ZkClient)
[2020-11-12 06:59:47,438] INFO Created zookeeper path /myKafka (kafka.server.KafkaServer)
[2020-11-12 06:59:47,439] INFO Terminate ZkClient event thread. (org.I0Itec.zkclient.ZkEventThread)
[2020-11-12 06:59:47,444] INFO Session: 0x100009c182d0001 closed (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,446] INFO EventThread shut down for session: 0x100009c182d0001 (org.apache.zookeeper.ClientCnxn)
[2020-11-12 06:59:47,447] INFO Initiating client connection, connectString=zookeeperCluster10:2181,zookeeperCluster11:2181,zookeeperCluster12:2181/myKafka sessionTimeout=6000 watcher=org.I0Itec.zkclient.ZkClient@3d74bf60 (org.apache.zookeeper.ZooKeeper)
[2020-11-12 06:59:47,451] INFO Starting ZkClient event thread. (org.I0Itec.zkclient.ZkEventThread)
[2020-11-12 06:59:47,462] INFO Waiting for keeper state SyncConnected (org.I0Itec.zkclient.ZkClient)
[2020-11-12 06:59:47,480] INFO Opening socket connection to server zookeeperCluster11/192.168.80.11:2181. Will not attempt to authenticate using SASL (unknown error) (org.apache.zookeeper.ClientCnxn)
[2020-11-12 06:59:47,486] INFO Socket connection established to zookeeperCluster11/192.168.80.11:2181, initiating session (org.apache.zookeeper.ClientCnxn)
[2020-11-12 06:59:47,507] INFO Session establishment complete on server zookeeperCluster11/192.168.80.11:2181, sessionid = 0x100009c182d0002, negotiated timeout = 6000 (org.apache.zookeeper.ClientCnxn)
[2020-11-12 06:59:47,507] INFO zookeeper state changed (SyncConnected) (org.I0Itec.zkclient.ZkClient)
[2020-11-12 06:59:48,029] INFO Cluster ID = ao6W1AN6SIaZD-x0PGk3yg (kafka.server.KafkaServer)
[2020-11-12 06:59:48,039] WARN No meta.properties file under dir /var/dabing/kafka/kafka-logs/meta.properties (kafka.server.BrokerMetadataCheckpoint)
[2020-11-12 06:59:48,214] INFO [ThrottledRequestReaper-Fetch]: Starting (kafka.server.ClientQuotaManager$ThrottledRequestReaper)
[2020-11-12 06:59:48,214] INFO [ThrottledRequestReaper-Produce]: Starting (kafka.server.ClientQuotaManager$ThrottledRequestReaper)
[2020-11-12 06:59:48,215] INFO [ThrottledRequestReaper-Request]: Starting (kafka.server.ClientQuotaManager$ThrottledRequestReaper)
[2020-11-12 06:59:48,381] INFO Log directory '/var/dabing/kafka/kafka-logs' not found, creating it. (kafka.log.LogManager)
[2020-11-12 06:59:48,569] INFO Loading logs. (kafka.log.LogManager)
[2020-11-12 06:59:48,617] INFO Logs loading complete in 48 ms. (kafka.log.LogManager)
[2020-11-12 06:59:49,792] INFO Starting log cleanup with a period of 300000 ms. (kafka.log.LogManager)
[2020-11-12 06:59:49,805] INFO Starting log flusher with a default period of 9223372036854775807 ms. (kafka.log.LogManager)
[2020-11-12 06:59:51,027] INFO Awaiting socket connections on 0.0.0.0:9092. (kafka.network.Acceptor)
[2020-11-12 06:59:51,032] INFO [SocketServer brokerId=2] Started 1 acceptor threads (kafka.network.SocketServer)
[2020-11-12 06:59:51,092] INFO [ExpirationReaper-2-Produce]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2020-11-12 06:59:51,092] INFO [ExpirationReaper-2-Fetch]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2020-11-12 06:59:51,152] INFO [ExpirationReaper-2-DeleteRecords]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2020-11-12 06:59:51,176] INFO [LogDirFailureHandler]: Starting (kafka.server.ReplicaManager$LogDirFailureHandler)
[2020-11-12 06:59:51,270] INFO [ExpirationReaper-2-topic]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2020-11-12 06:59:51,437] INFO [ExpirationReaper-2-Heartbeat]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2020-11-12 06:59:51,438] INFO [ExpirationReaper-2-Rebalance]: Starting (kafka.server.DelayedOperationPurgatory$ExpiredOperationReaper)
[2020-11-12 06:59:52,960] INFO [GroupCoordinator 2]: Starting up. (kafka.coordinator.group.GroupCoordinator)
[2020-11-12 06:59:52,985] INFO [GroupCoordinator 2]: Startup complete. (kafka.coordinator.group.GroupCoordinator)
[2020-11-12 06:59:52,995] INFO [GroupMetadataManager brokerId=2] Removed 0 expired offsets in 9 milliseconds. (kafka.coordinator.group.GroupMetadataManager)
[2020-11-12 06:59:53,072] INFO [ProducerId Manager 2]: Acquired new producerId block (brokerId:2,blockStartProducerId:2000,blockEndProducerId:2999) by writing to Zk with path version 3 (kafka.coordinator.transaction.ProducerIdManager)
[2020-11-12 06:59:53,168] INFO [TransactionCoordinator id=2] Starting up. (kafka.coordinator.transaction.TransactionCoordinator)
[2020-11-12 06:59:53,183] INFO [TransactionCoordinator id=2] Startup complete. (kafka.coordinator.transaction.TransactionCoordinator)
[2020-11-12 06:59:53,194] INFO [Transaction Marker Channel Manager 2]: Starting (kafka.coordinator.transaction.TransactionMarkerChannelManager)
[2020-11-12 06:59:53,318] INFO Creating /brokers/ids/2 (is it secure? false) (kafka.utils.ZKCheckedEphemeral)
[2020-11-12 06:59:53,333] INFO Result of znode creation is: OK (kafka.utils.ZKCheckedEphemeral)
[2020-11-12 06:59:53,347] INFO Registered broker 2 at path /brokers/ids/2 with addresses: EndPoint(kafkaCluster22,9092,ListenerName(PLAINTEXT),PLAINTEXT) (kafka.utils.ZkUtils)
[2020-11-12 06:59:53,352] WARN No meta.properties file under dir /var/dabing/kafka/kafka-logs/meta.properties (kafka.server.BrokerMetadataCheckpoint)
[2020-11-12 06:59:53,424] INFO [SocketServer brokerId=2] Started processors for 1 acceptors (kafka.network.SocketServer)
[2020-11-12 06:59:53,444] INFO Kafka version : 1.0.2 (org.apache.kafka.common.utils.AppInfoParser)
[2020-11-12 06:59:53,444] INFO Kafka commitId : 2a121f7b1d402825 (org.apache.kafka.common.utils.AppInfoParser)
[2020-11-12 06:59:53,445] INFO [KafkaServer id=2] started (kafka.server.KafkaServer)
10. 验证Kafka参数
- Cluster Id是一个唯一的不可变的标志符,用于唯一标志一个Kafka集群。
- 该Id最多可以有22个字符组成,字符对应于URL-safe Base64。
- Kafka 0.10.1版本及之后的版本中,在集群第一次启动的时候,
Broker从Zookeeper的<Kafka_ROOT>/cluster/id节点获取。如果该Id不存在,就自动生成一个新的。
11. 访问zookeeper集群上的任意节点:zkCli.sh
查看每个Broker的信息
[zk: localhost:2181(CONNECTED) 0] ls /
[myKafka, zookeeper]
![c9175718401cec2d80543dffcfbbf894.png](https://i-blog.csdnimg.cn/blog_migrate/8839e4372d9cc80d130171c936e8a69c.png)
查看zookeeper上的myKafka信息
[zk: localhost:2181(CONNECTED) 1] ls /myKafka
[cluster, controller, controller_epoch, brokers, admin, isr_change_notification, consumers, log_dir_event_notification, latest_producer_id_block, config]
![11729bf3af80ab1f9b38b666a9e0ace1.png](https://i-blog.csdnimg.cn/blog_migrate/104fe85cc768838af878498271759d7b.jpeg)
查看zookeeper上myKafka中的三个节点信息
[zk: localhost:2181(CONNECTED) 2] get /myKafka/brokers/ids/0
{"listener_security_protocol_map":{"PLAINTEXT":"PLAINTEXT"},"endpoints":["PLAINTEXT://kafkaCluster21:9092"],"jmx_port":-1,"host":"kafkaCluster21","timestamp":"1605182346116","port":9092,"version":4}
cZxid = 0x100000020
ctime = Thu Nov 12 06:59:06 EST 2020
mZxid = 0x100000020
mtime = Thu Nov 12 06:59:06 EST 2020
pZxid = 0x100000020
cversion = 0
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x20000a1ccba0001
dataLength = 198
numChildren = 0
![4dc27503d1ce66a11a7f95cccabf5599.png](https://i-blog.csdnimg.cn/blog_migrate/49d514fb1efda9738d4cbad052c6e02f.jpeg)
[zk: localhost:2181(CONNECTED) 3] get /myKafka/brokers/ids/1
{"listener_security_protocol_map":{"PLAINTEXT":"PLAINTEXT"},"endpoints":["PLAINTEXT://kafkaCluster20:9092"],"jmx_port":-1,"host":"kafkaCluster20","timestamp":"1605182384675","port":9092,"version":4}
cZxid = 0x100000027
ctime = Thu Nov 12 06:59:44 EST 2020
mZxid = 0x100000027
mtime = Thu Nov 12 06:59:44 EST 2020
pZxid = 0x100000027
cversion = 0
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x100009c182d0000
dataLength = 198
numChildren = 0
![144bcb1f025397661e2db63fec05f6ad.png](https://i-blog.csdnimg.cn/blog_migrate/851ab4999b923ee381f288a6b352d324.jpeg)
[zk: localhost:2181(CONNECTED) 4] get /myKafka/brokers/ids/2
{"listener_security_protocol_map":{"PLAINTEXT":"PLAINTEXT"},"endpoints":["PLAINTEXT://kafkaCluster22:9092"],"jmx_port":-1,"host":"kafkaCluster22","timestamp":"1605182393295","port":9092,"version":4}
cZxid = 0x10000002e
ctime = Thu Nov 12 06:59:53 EST 2020
mZxid = 0x10000002e
mtime = Thu Nov 12 06:59:53 EST 2020
pZxid = 0x10000002e
cversion = 0
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x100009c182d0002
dataLength = 198
numChildren = 0
![e30551d38c7f1519dddddad0276c21c2.png](https://i-blog.csdnimg.cn/blog_migrate/3e6644ed70e914d3e64b8df359f2e8cb.jpeg)
查看集群控制器所在节点
[zk: localhost:2181(CONNECTED) 5] get /myKafka/controller
{"version":1,"brokerid":0,"timestamp":"1605182345723"}
cZxid = 0x100000019
ctime = Thu Nov 12 06:59:05 EST 2020
mZxid = 0x100000019
mtime = Thu Nov 12 06:59:05 EST 2020
pZxid = 0x100000019
cversion = 0
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x20000a1ccba0001
dataLength = 54
numChildren = 0
[zk: localhost:2181(CONNECTED) 6]
![dde95f9219886d73463b42e971d8c20d.png](https://i-blog.csdnimg.cn/blog_migrate/ef3100c69becb4c50ca30373d5acd8fb.jpeg)
Kafka通过Zookeeper的分布式锁特性选举集群控制器
此时kafka的集群控制器在节点brokerid=0的节点上
![bfb984fcc72e187c4fbd0851bb7fd8f9.png](https://i-blog.csdnimg.cn/blog_migrate/968a65d39d50f31c7493e93d94b85fa0.jpeg)
演示epoch版本迭代,防止“脑裂”
每个新选出的控制器通过 Zookeeper 的条件递增操作获得一个全新的、数值更大的 controller epoch。其他 broker 在知道当前 controller epoch 后,如果收到由控制器发出的包含较旧epoch 的消息,就会忽略它们,以防止“脑裂”。
![6eaee4868ad8a1a739f7b5404968958c.png](https://i-blog.csdnimg.cn/blog_migrate/ead542ebcbe3a42719567088d08831e2.jpeg)
![56bab6ab57546124c100b08c9e5226a8.png](https://i-blog.csdnimg.cn/blog_migrate/dc8a8bdc704573a57bfaa80e11a434e2.jpeg)