搭建zookeeper-3.4.13 + kafka_2.11-2.0.0集群

zk/kafka集群， 每个集群三个server，分布在三个centos7系统虚机上，一个虚机一个zk一个kafka

三台内网虚机为192.168.1.101~103，每台虚机执行下面的操作

 

1.安装zk

cd /opt
sudo wget http://mirrors.hust.edu.cn/apache/zookeeper/zookeeper-3.4.13/zookeeper-3.4.13.tar.gz
sudo tar -zxvf zookeeper-3.4.13.tar.gz 
sudo chown -R linux用户名:linux用户名 zookeeper-3.4.13

2.配置zk：

sudo mkdir /opt/data/zookeeper
sudo mkdir /opt/log/zookeeper
sudo chown -R Linux用户名:Linux用户名 /opt/data/zookeeper
sudo chown -R Linux用户名:Linux用户名 /opt/log/zookeeper
cp /opt/zookeeper-3.4.13/conf/zoo_sample.cfg /opt/zookeeper-3.4.13/conf/zoo.cfg

#修改配置文件如下的内容
vim /opt/zookeeper-3.4.13/conf/zoo.cfg

    tickTime=2000
    initLimit=10
    syncLimit=5
    dataDir=/opt/data/zookeeper
    dataLogDir=/opt/log/zookeeper
    clientPort=2181
    server.1=192.168.1.101:2888:3888
    server.2=192.168.1.102:2888:3888
    server.3=192.168.1.103:2888:3888

#对server.1设置myid
echo "1" > /opt/data/zookeeper/myid
#对server.2设置myid
echo "2" > /opt/data/zookeeper/myid
#对server.3设置myid
echo "3" > /opt/data/zookeeper/myid

3.关闭防火墙

#方法1，直接关闭防火墙，一老永益，自己玩可以这么做，省心，不用来个程序就要开通端口号，有安全问题，所以自己玩可以，生产线上不能这么干
systemctl stop firewalld.service
systemctl disable firewalld.service


#方法2，开通zk通信的端口号，安全但是麻烦
firewall-cmd --permanent --zone=public --add-port=2181/tcp
firewall-cmd --permanent --zone=public --add-port=2888/tcp
firewall-cmd --permanent --zone=public --add-port=3888/tcp
firewall-cmd --reload
firewall-cmd --query-port=2181/tcp
firewall-cmd --query-port=2888/tcp
firewall-cmd --query-port=3888/tcp

 

4.启动zk

# 启动
cd /opt
/opt/zookeeper-3.4.13/bin/zkServer.sh start

    ZooKeeper JMX enabled by default
    Using config: /opt/zookeeper-3.4.13/bin/../conf/zoo.cfg
    Starting zookeeper ... STARTED


#查看状态和关闭，一台是leader，两台是follower
/opt/zookeeper-3.4.13/bin/zkServer.sh status

    ZooKeeper JMX enabled by default
    Using config: /opt/zookeeper-3.4.13/bin/../conf/zoo.cfg
    Mode: follower

    Mode: leader


/opt/zookeeper-3.4.13/bin/zkServer.sh stop

#使用zk自带的客户端连接
/opt/zookeeper-3.4.13/bin/zkCli.sh -server 192.168.1.101:2181

 

5.安装kafka

sudo wget http://mirrors.hust.edu.cn/apache/kafka/2.0.0/kafka_2.11-2.0.0.tgz
sudo tar -xzvf kafka_2.11-2.0.0.tgz 
sudo chown -R linux用户名:linux用户名 kafka_2.11-2.0.0

6.配置kafka

sudo mkdir /opt/log/kafka
sudo chown -R linux用户名:linux用户名/opt/log/kafka/

#配置文件如下broker.id=3和host.name每个server配置不一样
sudo vim /opt/kafka_2.11-2.0.0/config/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=3

############################# 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

host.name=192.168.1.103

# 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
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=/opt/log/kafka

# 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
message.max.byte=5242880
default.replication.factor=2
replica.fetch.max.bytes=5242880

# 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.1.101:2181,192.168.1.102:2181,192.168.1.103: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

7.启动kafka

cd /opt/kafka_2.11-2.0.0/
bin/kafka-server-start.sh config/server.properties &

8.测试kafka

cd /opt/kafka_2.11-2.0.0/

#创建一个topic
bin/kafka-topics.sh --create --zookeeper 192.168.1.101:2181 --replication-factor 3 --partitions 1 --topic first-topic

#查看刚刚创建的topic
bin/kafka-topics.sh --describe --zookeeper 192.168.1.101:2181 --topic first-topic
    Topic:first-topic	PartitionCount:1	ReplicationFactor:3	Configs:
	    Topic: first-topic	Partition: 0	Leader: 2	Replicas: 2,1,3	Isr: 2,1,3


#向创建的topic发消息，输入三条消息
bin/kafka-console-producer.sh --broker-list 192.168.1.101:9092 --topic first-topic
>message1
>message2
>message3 hellllllllllllo

#从创建的的topic消费消息
bin/kafka-console-consumer.sh --bootstrap-server 192.168.1.102:9092 --from-beginning --topic first-topic
出现以下信息证明消费成功，kafka大功告成
message1
message2
message3 hellllllllllllo

参考：

https://www.cnblogs.com/luotianshuai/p/5206662.html

https://zookeeper.apache.org/doc/current/zookeeperStarted.html

http://kafka.apache.org/quickstart