集群部署的基本流程
安装目标:(三台机子)
修改hosts(命令自行百度)
192.168.10.101 huawei1
192.168.10.102 huawei2
192.168.10.103 huawei3
下载安装包、解压安装包、修改配置文件、分发安装包、启动集群
集群部署的基础环境准备
安装前的准备工作（zk集群已经部署完毕）
关闭防火墙 (命令自行百度)
Kafka集群部署
下载安装包
http://kafka.apache.org/downloads.html
huawei1机子上创建安装空间
mkdir /export
mkdir /export/software在linux中使用wget命令下载安装包
wget http://mirrors.hust.edu.cn/apache/kafka/2.0.0/kafka_2.11-2.0.0.tgz
解压安装包
tar -zxvf /export/software/kafka_2.11-2.0.0.tgz -C /export/software/
cd /export/software/创建软连接
ln -s kafka_2.11-2.0.0 kafka修改配置文件
cp /export/software/kafka/config/server.properties
/export/software/kafka/config/server.properties.bak
vi /export/software/kafka/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=0
#用来监听链接的端口,producer或consumer将在此端口建立链接
port=9092
############################# 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
#处理网络请求的线程数量
num.network.threads=3
#用来处理磁盘IO的线程数量
num.io.threads=8
#用来发送套接字的缓冲区大小
socket.send.buffer.bytes=102400
#用来接受套接字的缓冲区大小
socket.receive.buffer.bytes=102400
#请求套接字的缓冲区大小
socket.request.max.bytes=104857600
############################# Log Basics #############################
#kafka运行日志存放的路径
log.dirs=/export/software/kafka/logs
#topic在当前broker上的分片个数
num.partitions=2
#用来恢复和清理data下数据的线程数量
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
#segment文件保留的最长时间,超时将被删除
num.retention.hours=168
#滚动生成新的segment文件的最大时间
log.roll.hours=168
############################# 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的ip和端口号
zookeeper.connect=huawei1:2181,huawei2:2181,huawei3: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.分别在其他两台机子上创建安装空间
huawei2机子上
mkdir /export
mkdir /export/softwarehuawei3机子上
mkdir /export
mkdir /export/software分发安装包
scp -r /export/software/kafka_2.11-2.0.0 huawei2:/export/software
scp -r /export/software/kafka_2.11-2.0.0 huawei3:/export/software然后分别在huawei2,huawei3上创建软连
cd /export/software/
ln -s kafka_2.11-2.0.0 kafka再次修改配置文件（重要）
依次修改各服务器上配置文件的的broker.id，分别是0,1,2不得重复。
启动集群
依次在各节点上启动kafka
前台启动:
bin/kafka-server-start.sh config/server.properties后台启动
bin/kafka-server-start.sh config/server.properties 1>/dev/null 2>&1 &Kafka常用操作命令
查看当前服务器中的所有topic
bin/kafka-topics.sh –list –zookeeper zk01:2181
创建topic
./kafka-topics.sh –create –zookeeper mini1:2181 –replication-factor 1 –partitions 3 –topic first
删除topic
sh bin/kafka-topics.sh –delete –zookeeper zk01:2181 –topic test
需要server.properties中设置delete.topic.enable=true否则只是标记删除或者直接重启。
通过shell命令发送消息
kafka-console-producer.sh –broker-list kafka01:9092 –topic itheima
通过shell消费消息
sh bin/kafka-console-consumer.sh –zookeeper zk01:2181 –from-beginning –topic test1
查看消费位置
sh kafka-run-class.sh kafka.tools.ConsumerOffsetChecker –zookeeper zk01:2181 –group testGroup
查看某个Topic的详情
sh kafka-topics.sh –topic test –describe –zookeeper zk01:2181