Kafka集群部署与使用

前置部署

Linux环境下Java JDK环境安装-CSDN博客

Linux环境下部署Zookeeper3.5.5集群部署-CSDN博客

一、kafka解压

cd /usr/local/soft
tar -zxvf kafka_2.11-2.3.0.tgz

二、配置系统环境变量

编辑系统环境变量

vi /etc/profile

增加如下内容

export KAFKA_HOME=/usr/local/soft/kafka_2.11-2.3.0
export PATH=$PATH:$KAFKA_HOME/bin

使环境变量生效

source /etc/profile

三、配置参数

创建日志文件夹

cd /usr/local/soft/kafka_2.11-2.3.0/
mkdir log
cd /usr/local/soft/kafka_2.11-2.3.0/config/

编辑配置文件vim 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

############################# 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://hadoop100: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/soft/kafka_2.11-2.3.0/log

# 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

# 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=hadoop100:2181,hadoop101:2181,hadoop102: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
delete.topic.enable=true

重点配置项

broker.id=0     #集群上需要改成和zk的myid一致

advertised.listeners=PLAINTEXT://hadoop100:9092  #集群上需要修改成自己的主机名

log.dirs=/usr/local/soft/kafka_2.11-2.3.0/log

zookeeper.connect=hadoop100:2181,hadoop101:2181,hadoop102:2181

delete.topic.enable=true

四、集群拷贝

scp -r /usr/local/soft/kafka_2.11-2.3.0 root@hadoop101:/usr/local/soft
scp -r /usr/local/soft/kafka_2.11-2.3.0 root@hadoop102:/usr/local/soft
scp /etc/profile root@hadoop101:/etc/profile
scp /etc/profile root@hadoop102:/etc/profile

更改集群每台机器的broker.id、advertised.listeners和系统环境生效source /etc/profile

每台机器上的id和zookeeper的myid一致

advertised.listeners改成自己的主机名或者ip

五、启动集群的Zookepper

zkStart.sh

六、启动集群Kafka

1、按个启动

所有节点都有启动Kafka

cd /usr/local/soft/kafka_2.11-2.3.0
bin/kafka-server-start.sh config/server.properties

2、脚本启动(强烈推荐)

cd /usr/local/soft/kafka_2.11-2.3.0/bin/
touch kf.sh
chmod +x kf.sh

脚本中添加如下内容

#!/bin/bash

case $1 in
"start")
	for i in hadoop100 hadoop101 hadoop102
	do
		echo "-- start $i kafka --"
		ssh $i "source /etc/profile;nohup /usr/local/soft/kafka_2.11-2.3.0/bin/kafka-server-start.sh -daemon /usr/local/soft/kafka_2.11-2.3.0/config/server.properties &"
	done
;;
"stop")
        for i in hadoop100 hadoop101 hadoop102
        do
                echo "-- stop $i kafka --"
                ssh $i "source /etc/profile;/usr/local/soft/kafka_2.11-2.3.0/bin/kafka-server-stop.sh"
        done
;;
esac

启动和关闭kafka集群命令

kf.sh start
kf.sh stop

FAQ:

1、启动出现占用

解决方案

七、测试

新打开一个窗口：

创建Topic：(创建一个名为test的topic，只有一个副本，一个分区。)

kafka-topics.sh --create --zookeeper hadoop100:2181, hadoop101:2181, hadoop102:2181 --replication-factor 1 --partitions 1 --topic test

列出所有Topic：

kafka-topics.sh -list -zookeeper hadoop100:2181    

启动Producer并发送消息：

kafka-console-producer.sh --broker-list hadoop100:9092 --topic test

可在下面书写需要发送的命令  

启动Consumer并接收消息：新打开一个窗口：

kafka-console-consumer.sh --bootstrap-server hadoop100:9092 --topic test --from-beginning