kafka集群搭建

1.环境说明

	操作系统：Centos7.x
	JDK:1.8
	zookeeper:zookpeeper-3.4.14
	kafka:kafka_2.12-2.2.1
	机器ip：172.16.180.12、172.16.180.17、172.16.180.3 
	以上说明的组件版本如下图所示：

2.搭建zookeeper集群

1.上传、解压包

上传zk包到/app目录下解压，并创建必要的路径和文件

# useradd kafka
# su – kafka
$ cd /app
$ tar -zxvf zookeeper-3.4.14.tar.gz
$ cd zookeeper-3.4.14
$ mkdir data
$ mkdir datalog
$ cd data
$ echo 1 > myid  # 在另外2台机器上myid文件的值依次分别为2、3
$ more myid
1

2.配置zoo.cfg

在zookeeper解压包下的conf目录下，有一个示例配置文件zoo_sample.cfg，我们可以复制一份，重命名为zoo.cfg，并在zoo.cfg文件中添加我们集群的相关配置信息：

$ cd /app/zookeeper-3.4.14/conf
$ mv zoo_sample.cfg zoo.cfg
$ vi zoo.cfg

修改配置信息如下，其余默认即可

# The number of milliseconds of each tick
tickTime=2000
# The number of ticks that the initial 
# synchronization phase can take
initLimit=10
# The number of ticks that can pass between 
# sending a request and getting an acknowledgement
syncLimit=5
# the directory where the snapshot is stored.
# do not use /tmp for storage, /tmp here is just 
# example sakes.
#dataDir=/tmp/zookeeper
# the port at which the clients will connect
clientPort=2181
# the maximum number of client connections.
# increase this if you need to handle more clients
#maxClientCnxns=60
#
# Be sure to read the maintenance section of the 
# administrator guide before turning on autopurge.
#
# http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance
#
# The number of snapshots to retain in dataDir
#autopurge.snapRetainCount=3
# Purge task interval in hours
# Set to "0" to disable auto purge feature
#autopurge.purgeInterval=1

dataDir=/app/zookeeper-3.4.14/data
dataLogDir=/app/zookeeper-3.4.14/dataLog
server.1=172.16.180.12:2888:2889
server.2=172.16.180.17:2888:2889
server.3=172.16.180.3:2888:2889
# 当启用自动清理功能后，ZooKeeper将只保留autopurge.snapRetainCount个最近的数据快照（dataDir）
#和对应的事务日志文件（dataLogDir），其余的将会删除掉。默认值是3。最小值也是3。
autopurge.snapRetainCount=20
#用于配置触发清理任务的时间间隔，以小时为单位。要启用自动清理，可以将其值设置为一个正整数（大于 1）。默认值是0。
autopurge.purgeInterval=24

3.启动zookeeper并进行测试

$ cd /app/zookeeper-3.4.14/bin
$ ./ zkServer.sh start  #3个节点依次启动即可
$ ./ zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /app/zookeeper-3.4.14/bin/../conf/zoo.cfg
Mode: follower
注：其中一台机器状态是leader,其余都是follower

本地windows上dos窗口测试zk：

C:\Users\zhaiwt>cd C:\Users\zhaiwt\Desktop\zookeeper\zookeeper-3.4.14\zookeeper-3.4.14\bin
C:\Users\zhaiwt\Desktop\zookeeper\zookeeper-3.4.14\zookeeper-3.4.14\bin>zkCli -server 172.16.180.12:2181

3.搭建kafka集群

1.上传、解压包

上传包至/app目录下解压

# su – kafka
$ cd /app
$ tar -zxvf kafka_2.12-2.2.1.tgz

2.修改配置文件

修改server.properties文件

$ cd /app/kafka_2.12-2.2.1/config/
$ vi 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.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://172.16.180.12: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().
host.name=172.16.180.12
advertised.listeners=PLAINTEXT://172.16.180.12: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=/app/kafka_2.12-2.2.1/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=localhost:2181
zookeeper.connect=172.16.180.12:2181,172.16.180.17:2181,172.16.180.3: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

delete.topic.enable=true
#message.max.byte=5242880

message.max.byte=5242880000
default.replication.factor=2
replica.fetch.max.bytes=5242880
# broker处理消息的最大线程数,一般情况下数量为cpu核数
num.network.threads=8
# broker处理磁盘IO的线程数,数值为cpu核数2倍
num.io.threads=16

# 每当producer写入10000条消息时，刷数据到磁盘 
log.flush.interval.messages=10000
# 每间隔1秒钟时间，刷数据到磁盘
log.flush.interval.ms=1000
# 保留三天，也可以更短 
log.retention.hours=24
# 段文件配置1GB，有利于快速回收磁盘空间，重启kafka加载也会加快(如果文件过小，则文件数量比较多，
# kafka启动时是单线程扫描目录(log.dir)下所有数据文件)
log.segment.bytes=1073741824

# 是否开启日志压缩
log.cleaner.enable=false

# 等待IO线程处理的请求队列最大数，若是等待IO的请求超过这个数值，那么会停止接受外部消息，应该是一种自我保护机制。
queued.max.requests=500
# replicas响应partition leader的最长等待时间，若是超过这个时间，
# 就将replicas列入ISR(in-sync replicas)，并认为它是死的，不会再加入管理中
replica.lag.time.max.ms=10000
# 如果follower落后与leader太多,将会认为此follower已经失效
replica.lag.max.messages=4000
# leader进行复制的线程数，增大这个数值会增加follower的IO
num.replica.fetchers=1

3.启动kafka集群

$ cd /app/kafka_2.12-2.2.1/bin
$ ./kafka-server-start.sh -daemon ../config/server.properties
#也可以写脚本vim start.sh 
#./kafka-server-start.sh -daemon ../config/server.properties  保存运行脚本即可启动集群
$ jps
28535 Jps
1689 QuorumPeerMain
683 Kafka

4.测试验证

$ cd /app/kafka_2.12-2.2.1/bin
$ ./kafka-topics.sh --create --zookeeper 172.16.180.12:2181,172.16.180.17:2181,172.16.180.3:2181 --replication-factor 2 --partitions 1 --topic test  ###创建主题
$ ./kafka-topics.sh --list --zookeeper 172.16.180.12:2181,172.16.180.17:2181,172.16.180.3:2181   ###查看主题
$ ./kafka-console-producer.sh --broker-list 172.16.180.12:9092,172.16.180.17:9092,172.16.180.3:9092 --topic test##进入生产主模式

$./kafka-console-consumer.sh --bootstrap-server 172.16.180.12:9092,172.16.180.17:9092,172.16.180.3:9092 --topic test --from-beginning##进入消费者模式，查看生产者发送的消息

5.测试验证(Windows)

本地Windows环境dos窗口测试：进入生产者模式发送消息：

进入消费者查看消息：

生产者：
kafka-console-producer.bat --broker-list 172.16.180.12:9092,172.16.180.17:9092,172.16.180.3:9092 --topic test

消费者：
kafka-console-consumer.bat --bootstrap-server 172.16.180.12:9092,172.16.180.17:9092,172.16.180.3:9092 --topic test --from-beginning