四、Kafka + Debezium 集群部署

（1）下载Kafka安装包并解压到指定目录

（2）修改配置文件，分配broker.id

（3）复制到其他节点，配置环境变量

（4）创建Kafka插件目录，解压debezium插件到插件目录

（5）修改配置文件，复制到其他节点

配置文件说明（server.properties）：

# 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编号，有且唯一
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

# 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
# 处理磁盘IO线程数量
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.
# topic默认分区数，建议设为broker倍数
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.
# 用来恢复和清理data下数据的线程数，数据目录位于RAID阵列中时，建议增加此值
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.
# 使用fsync同步
# 若不使用复制，可能丢失未刷新的数据
# 若刷新间隔时间偏大，会导致延迟峰值
# 刷新操作昂贵，若刷新间隔时间偏小，会导致过度查找
# The number of messages to accept before forcing a flush of data to disk
# buffer中消息条数，达到阈值将强制刷新到磁盘
#log.flush.interval.messages=10000

# The maximum amount of time a message can sit in a log before we force a flush
# 消息buffer的时间，达到阈值将强制刷新到磁盘
#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.
# zk链接
zookeeper.connect=localhost:2181

# Timeout in ms for connecting to zookeeper
# zk连接超时时间
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.
# 组协调器
# 新消费者加入时，重新平衡的最大延迟时间，生产环境建议设置3秒，消费者数量很多时很有用
group.initial.rebalance.delay.ms=0

以dataxc用户为例，脚本示例如下：

#!/bin/bash
# kafka.sh

# ---部署kafka集群---
nodes=(n101 n102 n103)
zk_connect='n101:2181,n102:2181,n103:2181'

#解压kafka到程序目录
cd /home/dataxc/sw && tar -zxvf kafka_2.13-2.8.0.tgz -C /home/dataxc/opt
cd /home/dataxc/opt && mv kafka_2.13-2.8.0 kafka

#复制kafka到其他节点
for node in ${nodes[*]:1}
	do
		scp -r /home/dataxc/opt/kafka dataxc@$node:/home/dataxc/opt/kafka
	done

#修改kafka配置文件
declare -i bid=0
for node in ${nodes[*]}
	do
		let bid+=1
		#配置broker.id、监听端口、zk集群地址、消息保留时长(hour)、偏移量保留时长(minute)
		ssh dataxc@$node sed -i "s/broker.id=0/broker.id=$bid/" /home/dataxc/opt/kafka/config/server.properties
		ssh dataxc@$node sed -i "s!#listeners=PLAINTEXT://:9092!listeners=PLAINTEXT://$node:9092!" /home/dataxc/opt/kafka/config/server.properties
		ssh dataxc@$node sed -i "s/zookeeper.connect=localhost:2181/zookeeper.connect=$zk_connect/" /home/dataxc/opt/kafka/config/server.properties
		ssh dataxc@$node 'sed -i "s/log.retention.hours=168/log.retention.hours=16800/" /home/dataxc/opt/kafka/config/server.properties;
		echo -e "offsets.retention.minutes=10080" >> /home/dataxc/opt/kafka/config/server.properties'
		#添加环境变量
		ssh dataxc@$node 'sed -i -e "/export JAVA_HOME=/a export KAFKA_HOME=/home/dataxc/opt/kafka" \
		-e "/^export PATH=/ s/$/\:\$KAFKA_HOME\/bin/" /home/dataxc/.bashrc;
		source /home/dataxc/.bashrc'
	done

:<<!
#启用外网访问
adips=(222.168.xx.xxx 222.168.xx.xxx 222.168.xx.xxx)
for adip in ${adips[*]}
	do
		ssh dataxc@$adip sed -i "s!#advertised.listeners=PLAINTEXT://your.host.name:9092!advertised.listeners=PLAINTEXT://$adip:9092!" /home/dataxc/opt/kafka/config/server.properties
	done
!

# ---部署debezium-connect---
bs='n101:9092,n102:9092,n103:9092'

#创建kafka插件目录
mkdir /home/dataxc/opt/kafka/plugins

#解压debezium-connector到指定目录
cd /home/dataxc/sw && find ./ -name "debezium-connector-*.tar.gz" -exec tar -zxvf {} -C /home/dataxc/opt/kafka/plugins \;

#添加kafka集群地址、创建插件目录
sed -i -e "s/bootstrap.servers=localhost:9092/bootstrap.servers=$bs/" \
-e '$a plugin.path=/home/dataxc/opt/kafka/plugins' /home/dataxc/opt/kafka/config/connect-distributed.properties

#复制到其他节点
for node in ${nodes[*]:1}
	do
		scp -r /home/dataxc/opt/kafka/plugins dataxc@$node:/home/dataxc/opt/kafka/plugins
		scp /home/dataxc/opt/kafka/config/connect-distributed.properties dataxc@$node:/home/dataxc/opt/kafka/config/connect-distributed.properties
	done

#启动kafka(所有节点)
#cd ${KAFKA_HOME} && bin/kafka-server-start.sh -daemon config/server.properties

#启动kafka-connect(所有节点)
#cd ${KAFKA_HOME} && bin/connect-distributed.sh -daemon config/connect-distributed.properties

#end