Kafka—安装

一、环境搭建

　　kafka 版本： kafka_2.12

　　管控台：kafkaManger 2.0.0.2

　　协调服务：zookeeper-3.5.7

　　kafka 环境验证（控制台操作）

　　1、准备 3 台虚拟机，并且 zookeeper 集群已启动（具体安装请见我写的另一篇）

　　

　　2、下载 kafka 安装包 https://archive.apache.org/dist/kafka/2.2.1/kafka_2.12-2.2.1.tgz

　　

　　解压 kafka 到  usr/local

　　

　　修改配置文件

　　

 vim server.properties 

　　 修改内容

############################# Server Basics #############################

# The id of the broker. This must be set to a unique integer for each broker.
# 如果要组成集群，id不能相同
broker.id=0

############################# 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
# 端口
port=9092
host.name=192.168.2.200
# 备用地址
dvertised.host.name=192.168.2.200

# 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=/usr/local/kafka/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=5

# 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.2.200:2181,192.168.2.201:2181,192.168.2.202: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

 　　3、启动 kafak（ & 后台启动）

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

　　

 二、安装管控台

　　

 　　1、解压文件

unzip kafka-manager-2.0.0.2.zip -d /usr/local/kafka-manager

 　　2、修改配置文件

　　

vim application.conf

# zookeeper 集群地址
kafka-manager.zkhosts="192.168.2.200:2181,192.168.2.201:2181,192.168.2.202:2181" 

　　3、启动

./bin/kafka-manager &

　　

　　浏览器访问控制台：默认端口号：9000

　　http://192.168.2.200:9000/

　　

 　　4、添加集群，填写相应信息，点击 save 按钮

　　

 　　

 　　刷新页面，就出现了

　　

　　5、集群验证

　　　　1、创建topic "test" 5个分区，1个副本

　　

 　　

 　　

 　　

 　　

 　　有5个分区，接下来查看服务器日志，分别存在每一个服务器上。

　　

　　

　　

　　2、测试消息发送与接收

　　　　发送

cd /usr/local/kafka/bin

# --broker-list broker 集群地址，多个用逗号隔开
./kafka-console-producer.sh --broker-list 192.168.2.200:9092 --topic test

 　　

　　接收

# --bootstrap-server broker 集群地址，多个用逗号隔开
./kafka-console-consumer.sh --bootstrap-server 192.168.2.200:9092 --topic test