kafka2.1.0高可用HA叢集搭建方法
阿新 • • 發佈：2019-01-07
kafka2.1.0高可用HA叢集搭建方法
（一）安裝zookeeper3.4.6叢集
詳見安裝方法地址：https://blog.csdn.net/hsg77/article/details/80945493
（二）安裝kafka2.1.0
下載地址：
http://kafka.apache.org/downloads
我選擇的Scala 2.11 - kafka_2.11-2.1.0.tgz (asc, sha512)下載
解壓到節點中
tar -zxvf kafka_2.11-2.1.0.tgz
mv kafka_2.11-2.1.0 kafka
配置引數config/server.properties
主要修改的引數
broker.id=1 #node111為id=1,node112為id=2,node113為id=3
zookeeper.connect=node111:2181,node112:2181,node113:2181
num.partitions=4
啟動kafka叢集
runCmd.sh "zkServer.sh start" zookeeper runCmd.sh "kafka-server-start.sh -daemon /usr/cwgis/app/kafka/config/server.properties" all [[email protected] ~]# runCmd.sh "jps" all *******************node111*************************** 6086 Kafka 6167 Jps 2287 QuorumPeerMain *******************node112*************************** 2209 QuorumPeerMain 5169 Kafka 5586 Jps *******************node113*************************** 5152 Kafka 2201 QuorumPeerMain 5565 Jps
建立kafka主題和生產者寫入訊息
[[email protected] ~]# kafka-topics.sh --create --zookeeper node111:2181,node112:2181,node113:2181 --replication-factor 3 --partitions 4 --topic topic2
Created topic "topic2".
[[email protected] ~]# kafka-topics.sh --describe --zookeeper node111:2181 --topic topic1
[[email protected] kafka消費者檢視訊息
[[email protected] ~]# kafka-console-consumer.sh --bootstrap-server node111:9092 --from-beginning --topic topic2
hello kafka
hello java
停止kafka叢集
[[email protected] ~]# runCmd.sh "kafka-server-stop.sh" all
*******************node111***************************
*******************node112***************************
*******************node113***************************
[[email protected] ~]# runCmd.sh "jps" all
*******************node111***************************
8592 Jps
2287 QuorumPeerMain
*******************node112***************************
2209 QuorumPeerMain
6470 ConsoleConsumer
6847 Jps
*******************node113***************************
5680 Jps
2201 QuorumPeerMain
[[email protected] ~]#
node111節點具體引數
# 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
#host.name=node111
############################# 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://node111: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://node111: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/cwgis/app/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=4
# 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=node111:2181,node112:2181,node113: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
(三)kafka web管理安裝
這裡選擇的是yahoo 的kafka-mamager工具
先下載二進位制包kafka-manager-1.3.3.7.zip
下載地址：連結：https://pan.baidu.com/s/1qYifoa4 密碼：el4o
解壓到安裝目錄/usr/cwgis/app/kafka-manager-1.3.3.7
bin conf lib share …
編輯conf/application.conf
新增程式碼：kafka-manager.zkhosts=“node111:2181,node112:2181,node113:2181”
#kafka-manager.zkhosts="localhost:2181"
#kafka-manager.zkhosts=${?ZK_HOSTS}
kafka-manager.zkhosts="node111:2181,node112:2181,node113:2181"
啟動kafka-manager方法
後臺執行命令的格式為:nohup command &
chmod 777 kafka-manager
nohup ./kafka-manager &
然後任意shell 命令回到shell狀態來執行其他shell 如：ls
kafka-manager 預設的埠是9000，可通過 -Dhttp.port，指定埠; -Dconfig.file=conf/application.conf指定配置檔案:
nohup bin/kafka-manager -Dconfig.file=conf/application.conf -Dhttp.port=8080
nohup ./kafka-manager -Dconfig.file=conf/application.conf -Dhttp.port=8080
訪問kafka-manager web頁面地址：
http://192.168.30.111:9000/
新增族引數
Add Cluster
Cluster Zookeeper Hosts=node111:2181,node112:2181,node113:2181
Kafka Version=0.8.2.1
儲存save
—the—end—
參考地址：
https://github.com/yahoo/kafka-manager/releases
https://www.cnblogs.com/dadonggg/p/8205302.html