kafka1.1.0版本集群搭建（kafka_2.11-1.1.0）

• zookeeper-3.4.6
• kafka_2.11-1.1.0

zookeeper-3.4.6安装

1. 解压zookeeper-3.4.6.tar.gz文件到/data/zookeeper目录下，修改配置文件zoo.cfg

wget http://www.apache.org/dist/zookeeper/zookeeper-3.4.6/zookeeper-3.4.6.tar.gz
tar -zxvf zookeeper-3.4.6.tar.gz
mv zookeeper-3.4.6 zookeeper
cd zookeeper
cp conf/zoo_sample.cfg conf/zoo.cfg

2. 修改配置文件zoo.cfg

主要变更：

clientPort=2182
dataDir=/data/zookeeper/data
dataLogDir=/data/zookeeper/logs
server.1=192.168.97.211:2555:3555
server.2=192.168.97.212:2556:3556
server.3=192.168.97.213:2557:3557

修改后配置如下：

# 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=/data/zookeeper/data
dataLogDir=/data/zookeeper/logs
# the port at which the clients will connect
clientPort=2182
# 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.97.211:2555:3555
server.2=192.168.97.212:2556:3556
server.3=192.168.97.213:2557:3557

3. 分别在目录下建立data、logs目录，在data目录下建立myid文件，指定当前server的id，同配置文件:

mkdir data
mkdir logs
echo "1" >> ./data/myid

4. 分别拷贝到其他的服务器下面，并修改myid文件，对应配置文件中的id。

5. 分别启动每个节点，查看集群的日志文件zookeeper.out查看是否有错误。

./bin/zkServer.sh start

kafka1.1.0安装

1. 下载kafka1.1.0版本，并解压到当前目录

wget https://archive.apache.org/dist/kafka/1.1.0/kafka_2.11-1.1.0.tgz
tar -zxvf kafka_2.11-1.1.0.tgz

2. 修改配置文件config/server.properties

主要变更：

#是否允许删除topic，默认false不能手动删除
delete.topic.enable=true
listeners=PLAINTEXT://:9192
num.partitions=3
log.dirs=/data/kafka_2.11-1.1.0/logs
zookeeper.connect=192.168.97.211:2182,192.168.97.212:2182,192.168.97.213:2182

修改后配置如下：

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

#是否允许删除topic，默认false不能手动删除
delete.topic.enable=true

# The id of the broker. This must be set to a unique integer for each broker.
broker.id=212

############################# 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://:9192

# 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=/data/kafka_2.11-1.1.0/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=3

# 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=192.168.97.211:2182,192.168.97.212:2182,192.168.97.213:2182

# 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

kafka的简单使用

1. 启动kafka，正常启动可见【编写启动脚本】

./bin/kafka-server-start.sh config/server.properties &

2. 创建topic主题

./bin/kafka-topics.sh --create --zookeeper 192.168.97.211:2182,192.168.97.212:2182,192.168.97.213:2182 --replication-factor 3 --partitions 3 --topic TestTopic

命令说明：
–topic 定义topic名
–replication-factor 定义副本数
–partitions 定义分区数

3. 查看topic主题详情

./bin/kafka-topics.sh --describe --zookeeper 192.168.97.211:2182,192.168.97.212:2182,192.168.97.213:2182 --topic TestTopic

4. 列出当前所有topic

./bin/kafka-topics.sh --list --zookeeper 192.168.97.211:2182,192.168.97.212:2182,192.168.97.213:2182

5. 创建生产者

./bin/kafka-console-producer.sh --broker-list 192.168.97.211:9192,192.168.97.212:9192,192.168.97.213:9192 --topic TestTopic

6. 创建消费者

旧消费者命令

./bin/kafka-console-consumer.sh --zookeeper 192.168.97.211:2182,192.168.97.212:2182,192.168.97.213:2182  --from-beginning --topic TestTopic

新消费者命令

./bin/kafka-console-consumer.sh --bootstrap-server 192.168.97.211:9192,192.168.97.212:9192,192.168.97.213:9192  --from-beginning --topic TestTopic

参数说明：
–from-beginning：会把TestTopic主题中以往所有的数据都读取出来。根据业务场景选择是否增加该配置。

7. 删除topic

./bin/kafka-topics.sh --zookeeper 192.168.97.211:2182,192.168.97.212:2182,192.168.97.213:2182  --delete --topic TestTopic

8. 停止kafka 注意这个停止脚本可能不能用，需要检查一下

./bin/kafka-server-stop.sh stop

9. 编写启动脚本

nohup /data/kafka_2.11-1.1.0/bin/kafka-server-start.sh /data/kafka_2.11-1.1.0/config/server.properties > /dev/null 2>&1 &

参数优化

修改kafka启动参数配置bin/kafka-server-start.sh

export KAFKA_HEAP_OPTS="-Xmx3G -Xms3G"
if [ "x$KAFKA_HEAP_OPTS" = "x" ]; then
    export KAFKA_HEAP_OPTS="-Xmx1G -Xms1G"
fi

参考：https://www.cnblogs.com/frankdeng/p/9403883.html