2.kafka集羣環境搭建

2.1.集羣主機規劃

序號	機器名稱	ip/mac地址	硬件資源	安裝服務
1	cdh1 root/server123	192.168.80.100，00:50:56:2B:5B:EF	cpu：2核 ， 內存：2.5g ，硬盤20g ，網卡：千兆網卡	jdk、zookeeper、kafka
2	cdh2 root/server123	192.168.80.101，00:50:56:39:23:67	cpu：2核 ， 內存：2.5g ，硬盤20g ，網卡：千兆網卡	jdk、zookeeper、kafka
3	cdh3 root/server123	192.168.80.102，00:50:56:3E:3A:0B	cpu：2核 ， 內存：2.5g ，硬盤20g ，網卡：千兆網卡	jdk、zookeeper、kafka

說明：集羣主機之間須要配置ssh免密碼登陸

免密登陸參考:https://www.cnblogs.com/luzhanshi/p/13369797.html

安裝zookeeper集羣

下載zookeeper

#zookeeper官網地址：
 http://zookeeper.apache.org/
 一個分佈式協調服務,管理咱們的集羣
官網提供配置說明:https://zookeeper.apache.org/doc/current/zookeeperStarted.html

上傳解壓

解壓到

/usr/local/zookeeper/:

配置

菜單進入conf目錄下面,將zoo_sample.cfg複製一份到本目錄並更名爲zoo.cfg

 vim編輯該配置文件:

#編輯文件：
    vim zoo.cfg
    
---------------------------------------------------------------------------- # The number of milliseconds of each tick #時間單元，zk中的全部時間都是以該時間單元爲基礎，進行整數倍配置(單位是毫秒,下面配置的是2秒)
tickTime=2000
# The number of ticks that the initial
# synchronization phase can take
#follower在啓動過程當中，會從leader同步最新數據須要的最大時間。若是集羣規模比較大，能夠調大該參數
initLimit=10
# The number of ticks that can pass between
# sending a request and getting an acknowledgement
#leader與集羣中全部機器進行心跳檢查的最大時間。若是超出該時間，某follower沒有迴應，則說明該follower下線
syncLimit=5
# the directory where the snapshot is stored.
# do not use /tmp for storage, /tmp here is just # example sakes. #事務日誌輸出目錄
dataDir=/usr/local/zookeeper/zookeeper-3.4.5-cdh5.14.0/zkdatas

# the port at which the clients will connect #客戶端鏈接端口
clientPort=2181
# 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
#須要保留文件數目，默認就是3個
autopurge.snapRetainCount=3
# Purge task interval in hours
# Set to "0" to disable auto purge feature
#自動清理事務日誌和快照文件的頻率，這裏是1個小時
autopurge.purgeInterval=1

#集羣服務器配置，數字1/2/3須要與myid文件一致。右邊兩個端口，2888表示數據同步和通訊端口；3888表示選舉端口
server.1=域名1:2888:3888
server.2=域名2:2888:3888
server.3=域名3:2888:3888

上面個人域名設置是my.server1;my.server2;my.server3

建立數據目錄和myid

#建立數據存儲目錄：
    mkdir -p /usr/local/zookeeper/zookeeper-3.4.5-cdh5.14.0/zkdatas 
#建立myid: 
　　cd/usr/local/zookeeper/zookeeper-3.4.5-cdh5.14.0/zkdatas 
　　touch myid
　　並編輯myid內容爲1

分發到其它主機節點

注意,下面語句是以個人其餘兩天服務器主機別名分別是server02和server03爲基礎

#分發到node02節點，並修改myid內容爲2：
     scp -r zookeeper-3.4.5-cdh5.14.0/ server02:$PWD

#分發到node03節點，並修改myid內容爲3：
     scp -r zookeeper-3.4.5-cdh5.14.0/ server03:$PWD

啓動zookeeper集羣

分別在node01/node02/node03節點啓動/中止：
    /usr/local/zookeeper/zookeeper-3.4.5-cdh5.14.0/bin/zkServer.sh start/stop

    
#查看集羣狀態：
    /usr/local/zookeeper/zookeeper-3.4.5-cdh5.14.0/bin/zkServer.sh status

 若是在查看狀態的時候出現以下錯誤:

 出現這個問題有一下幾種可能性：

 1.防火牆沒有關閉，就是對應的集羣端口沒有開放，因此各個節點之間沒辦法通訊（zoo.cfg中最後本身配置的內容(包括2888端口和3888端口)以及zookeeper本身的2181端口）； 

 2.zookeeper中conf目錄下的zoo.cfg配置文件有問題，查看日誌dataLog文件的目錄，以及data數據文件的目錄是否正確； 

 3.myid文件中的內容是否和zoo.cfg中配

開放上述端口:

再次測試:

 

安裝kafka集羣

下載kafka

#kafka官網：
http://kafka.apache.org/
http://kafka.apache.org/downloads

上傳解壓

 

 

 

 

 

 

配置

進入

/usr/local/kafka/kafka_2.11-1.0.0/config

 

 

 

# 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在集羣中的惟一標識，不能重複
broker.id=0
#端口
port=9092
#broker主機地址
host.name=server1

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

# The number of threads that the server uses for receiving requests from the network and sending responses to the network
#broker處理消息的線程數
num.network.threads=3

# The number of threads that the server uses for processing requests, which may include disk I/O
#broker處理磁盤io的線程數
num.io.threads=8

# The send buffer (SO_SNDBUF) used by the socket server
#socket發送數據緩衝區
socket.send.buffer.bytes=102400

# The receive buffer (SO_RCVBUF) used by the socket server
#socket接收數據緩衝區
socket.receive.buffer.bytes=102400

# The maximum size of a request that the socket server will accept (protection against OOM)
#socket接收請求最大值
socket.request.max.bytes=104857600


############################# Log Basics #############################

# A comma seperated list of directories under which to store log files
#kafka數據存放目錄位置，多個位置用逗號隔開
log.dirs=/usr/local/kafka/kafka_2.11-1.0.0/kfk-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.
#topic默認的分區數
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 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 due to age
#消息日誌最大存儲時間，這裏是7天
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.
#每一個日誌段文件大小，這裏是1g
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集羣地址
zookeeper.connect=server1:2181,server2:2181,server3:2181

# Timeout in ms for connecting to zookeeper
#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

建立數據存儲目錄

#建立數據存儲目錄：
    mkdir -p /usr/local/kafka/kafka_2.11-1.0.0/kfk-logs

分發到其它主機節點

先在server2和server3上建立對應目錄:

    mkdir -p /usr/local/kafka/kafka_2.11-1.0.0

而後:

#分發到node02節點：
　　
    scp -r /usr/local/kafka/kafka_2.11-1.0.0/ server2:$PWD

#分發到node03節點： 
　　 scp -r /usr/local/kafka/kafka_2.11-1.0.0/ server3:$PWD 

修改其它節點配置文件

#server2節點
cd /usr/local/kafka/kafka_2.11-1.0.0/config

vim server.properties
----------------------------------------------------
# The id of the broker. This must be set to a unique integer for each broker.
broker.id=1
port=9092

#server3節點
cd /usr/local/kafka/kafka_2.11-1.0.0/config

vim server.properties
----------------------------------------------------
# The id of the broker. This must be set to a unique integer for each broker.
broker.id=2
port=9092

啓動kafka集羣

#分別在三臺節點執行：node01/node02/node03
 ##啓動kafka集羣-daemon(之後臺服務方式啓動) 後面跟的是以配置文件啓動
/usr/local/kafka/kafka_2.11-1.0.0/bin/kafka-server-start.sh -daemon /usr/local/kafka/kafka_2.11-1.0.0/config/server.properties

 ## 中止kafka集羣
/usr/local/kafka/kafka_2.11-1.0.0/bin/kafka-server-stop.sh

 

查看是否有kafka進程

 

kafka基本使用

交互式命令使用:

 

查看topic

#查看topic 列表：
    /usr/local/kafka/kafka_2.11-1.0.0/bin/kafka-topics.sh --list --zookeeper server1:2181,server2:2181,server3:2181
    
#查看指定topic：
/usr/local/kafka/kafka_2.11-1.0.0/bin/kafka-topics.sh  --describe --zookeeper server1:2181,server2:2181,server3:2181 --topic itcast_topic
    
#建立topic
# --create：表示建立
# --zookeeper 後面的參數是zk的集羣節點
# --replication-factor 1 ：表示複本數
# --partitions 1：表示分區數
# --topic itheima_topic：表示topic的主題名稱

/usr/local/kafka/kafka_2.11-1.0.0/bin/kafka-topics.sh --create --zookeeper server1:2181,server2:2181,server3:2181 --replication-factor 1 --partitions 1 --topic oc_itheima_topic

#刪除topic
/usr/local/kafka/kafka_2.11-1.0.0/bin/kafka-topics.sh --delete --zookeeper server1:2181,server2:2181,server3:2181 --topic itheima_topic

建立生產者

#建立生產者，生產消息
/usr/local/kafka/kafka_2.11-1.0.0/bin/kafka-console-producer.sh --broker-list server1:9092,server2:9092,server3:9092 --topic oc_itheima_topic

 

 發送消息:

建立消費者

#建立消費者，消費消息：
/usr/local/kafka/kafka_2.11-1.0.0/bin/kafka-console-consumer.sh --bootstrap-server server1:9092,server2:9092,server3:9092 --topic oc_itheima_topic --consumer-property group.id=my-consumer-g  --partition 0 --offset 0

 

 

 

 

 

 

 

$PWD