準備

• 1.kafka_2.10-0.10.1.1.tgz
• 2.安裝配置好的Zookeeper-3.4.10分散式叢集
  mini1：192.168.213.133
  mini2：192.168.213.134
  mini3：192.168.213.135

安裝

• 1.解壓kafka_2.10-0.10.1.1.tgz安裝包實現安裝

# tar -zxvf kafka_2.10-0.10.1.1.tgz -C /usr/local/bigdata

• 2.重新命名

# cd /usr/local/bigdata
# mv kafka_2.10-0.10.1.1 kafka-1.10.1.1

配置

• 1.配置kafka環境變數

# vim /etc/profile

新增記錄：

KAFKA_HOME=/usr/local/bigdata/kafka-0.10.1.1
export PATH=$KAFKA_HOME/bin:$PATH

使配置檔案生效：

# source /etc/profile

• 2.修改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=1

# Switch to enable topic deletion or not, default value is false
delete.topic.enable=true

############################# 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 = security_protocol://host_name:port
#   EXAMPLE:
#     listeners = PLAINTEXT://your.host.name:9092
#listeners=PLAINTEXT://:9092
port=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

# The number of threads handling network requests
num.network.threads=3

# The number of threads doing 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 seperated list of directories under which to store log files
log.dirs=/usr/local/bigdata/kafka-0.10.1.1/kafkadata/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

############################# 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. T hroughput: The flush is generally the most expensive operation, and a small flush interval may lead to exceessive 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
log.retention.hours=168

# A size-based retention policy for logs. Segments are pruned from the log as long as the remaining
# segments don't drop below log.retention.bytes.
#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=mini1:2181,mini2:2181,mini3:2181

# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000

# 此處的host.name為本機IP(重要),如果沒有配置，則客戶端會丟擲Producer connection to localhost:9092 unsuccessful錯誤！
host.name=mini1

• 3.分發安裝包

# scp -r /usr/local/bigdata/kafka-0.10.1.1 mini2:/usr/local/bigdata/
# scp -r /usr/local/bigdata/kafka-0.10.1.1 mini3:/usr/local/bigdata/

• 4.再次修改server.properties檔案

依次修改伺服器配置檔案中的broker.id，不能重複，比如1,2,3...

啟動

# kafka-server-start.sh

常用命令

   檢視當前伺服器中的所有topic
kafka-topics.sh --list --zookeeper mini1:2181
   建立topic
kafka-topics.sh --create --zookeeper mini1:2181 --replication-factor 1 --partitions 3 --topic test
   刪除topic
kafka-topics.sh --delete --zookeeper mini1:2181 --topic test
需要server.properties中設定delete.topic.enable=true，否則只是標記刪除
   通過shell命令傳送訊息
kafka-console-producer.sh --broker-list mini1:9092 --topic test
   通過shell消費訊息
kafka-console-consumer.sh --zookeeper mini1:2181 --from-beginning --topic test
   檢視消費位置
kafka-run-class.sh kafka.tools.ConsumerOffsetChecker --zookeeper mini1:2181 --group testGroup
   檢視某個Topic的詳情
kafka-topics.sh --topic test --describe --zookeeper mini1:2181

Over