说明：kafka采用的是2.12-2.5.0，zookeeper采用的是3.5.10。
闭坑：搭建时采用了zookeeper 3.3.6 发现kafka集群不能通信，修改为3.5.10后正常。
zookeeper集群搭建
首先准备了3台服务器，服务器的ip如下
- 192.168.0.1 8.144.56.1
- 192.168.0.2 8.144.56.2
- 192.168.0.3 8.144.56.3
zookeeper 下载网址：
https://archive.apache.org/dist/zookeeper/zookeeper-3.5.10/
1、存放位置：/usr/local/zookeeper （3台都是同位置）
解压命令：tar -zxvf
apache-zookeeper-3.5.10-bin.tar.gz
2、修改conf/zoo.cfg文件（3台都是这么修改）
将zoo_sample.cfg文件重命名为zoo.cfg
修改：dataDir路径并在后面追加server.1、server.2、server.3
# 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=/usr/local/zookeeper/apache-zookeeper-3.5.10-bin/data
# 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
server.1=192.168.0.1:2888:3888
server.2=192.168.0.2:2888:3888
server.3=192.168.0.3:2888:38883、创建myid文件，在data目录下，注意是在dataDir中指定的路径
例如我的是：
/usr/local/zookeeper/apache-zookeeper-3.5.10-bin/data
这个1对应的就是server.1，所以另外2台服务器应该创建为2,3。
4、启动zookeeper bin目录下
命令：
./zkServer.sh start
./zkServer.sh status
./zkServer.sh stopkafka集群搭建
下载网址：
https://archive.apache.org/dist/kafka/2.5.0/kafka_2.12-2.5.0.tgz
1、存放位置：/usr/local/kafka（3台都是同位置）
解压命令：tar -zxvf kafka_2.12-2.5.0.tgz
2、创建data目录，存储数据
3、修改config下的server.properties
配置中的broker.id要跟上面zookeeper创建的myid内容一致。
listeners、advertised.listeners换成自己的内网ip以及外网ip，如果不希望外网访问，可以去掉。
log.dirs指定为上面创建的data路径
zookeeper.connect配置为zookeeper地址
4、启动 bin目录下
./kafka-server-start.sh -daemon ../config/server.properties
./kafka-server-stop.sh详细的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
host.name=192.168.0.1
advertised.host.name=8.144.56.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=INTERNAL://0.0.0.0:9092,EXTERNAL://0.0.0.0:19092
# 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=INTERNAL://192.168.0.1:9092,EXTERNAL://8.144.56.1:19092
# 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
listener.security.protocol.map=INTERNAL:PLAINTEXT,EXTERNAL:PLAINTEXT
inter.broker.listener.name=INTERNAL
# The number of threads that the server uses for receiving requests from the network and sending responses to the network
num.network.threads=10
# The number of threads that the server uses for processing requests, which may include disk I/O
num.io.threads=20
# The send buffer (SO_SNDBUF) used by the socket server
socket.send.buffer.bytes=33554432
# The receive buffer (SO_RCVBUF) used by the socket server
socket.receive.buffer.bytes=33554432
# The maximum size of a request that the socket server will accept (protection against OOM)
socket.request.max.bytes=209715200
############################# Log Basics #############################
# A comma separated list of directories under which to store log files
log.dirs=/usr/local/kafka/kafka_2.12-2.5.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=4
############################# 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=3
transaction.state.log.replication.factor=3
transaction.state.log.min.isr=3
############################# 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=192.168.0.1:2181,192.168.0.2:2181,192.168.0.3:2181/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