????????因?yàn)轫?xiàng)目中要使用KAFKA,自己搭建一個(gè)單機(jī)版，作測(cè)試服務(wù)器使用，已經(jīng)過測(cè)試，可以使得，分享有需要的朋友。
一、 kafka環(huán)境搭建
????????下載kafka單機(jī)版，可以使用源碼的方式和安裝包的方式安裝。使用安裝包的方式進(jìn)行安裝，只需要進(jìn)行解壓運(yùn)行即可。
源碼下載地址：https://archive.apache.org/dist/kafka/2.5.0/kafka-2.5.0-src.tgz
安裝包下載地址：https://archive.apache.org/dist/kafka/2.5.0/kafka_2.12-2.5.0.tgz
(1)、解壓kafka_2.12-2.5.0.tgz，得到 "kafka_2.12-2.5.0 " 文件夾。
tar -zxvf kafka_2.12-2.5.0.tgz
?(2)、kafka需要安裝zookeeper使用，但kafka集成zookeeper,在單機(jī)搭建時(shí)可直接使用。使用需配置kafka_2.12-2.5.0/config 下的“zookeeper.properties” ??
cd kafka_2.12-2.5.0/config
注:經(jīng)過部署發(fā)現(xiàn) kafka必須配置zookeeper ?否則無法啟動(dòng) ?無論是單機(jī)還是集群,必須,必須,必須開啟
# 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.
# the directory where the snapshot is stored.
dataDir=/tmp/zookeeper
# the port at which the clients will connect
clientPort=2181
# disable the per-ip limit on the number of connections since this is a non-production config
maxClientCnxns=0
# Disable the adminserver by default to avoid port conflicts.
# Set the port to something non-conflicting if choosing to enable this
admin.enableServer=false
# admin.serverPort=8080
?(3)、配置"zookeeper.properties"。修改dataDir和clientPort。前者是快照存放地址(自己隨意配置)，后者是客戶端連接zookeeper服務(wù)的端口。默認(rèn)端口2181 最好默認(rèn)不修改
vim kafka_2.12-2.5.0/config/zookeeper.properties
?(4)、配置kafka_2.12-2.5.0/config下的“server.properties”，修改log.dirs和zookeeper.connect。前者是日志存放文件夾，后者是zookeeper連接地址（端口和clientPort保持一致）。
vim kafka_2.12-2.5.0/config/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 默認(rèn)為本機(jī)IP 端口默認(rèn)9092 如圖:
listeners=PLAINTEXT://127.0.0.1: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
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=/tmp/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=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 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=localhost:2181
# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=18000
############################# 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
?
?注:這里的web 為服務(wù)器的hostname 能不能寫ip呢?大家可以試試,我這里寫的是我的hostname
?注:若需要外部訪問 ?一定需要配置listeners ? 默認(rèn)為本機(jī)IP ? 端口默認(rèn)9092 ?如圖:
?到此，kafka的單機(jī)環(huán)境就搭建成功了。
二 kafka的相關(guān)命令(kafka_2.12-2.5.0的根目錄下執(zhí)行)
(1)開啟kafka自帶zookeeper
前臺(tái)運(yùn)行(顯示Kafka內(nèi)部打印或異常信息)：./bin/zookeeper-server-start.sh ./config/zookeeper.properties
./bin/zookeeper-server-start.sh ./config/zookeeper.properties
后臺(tái)運(yùn)行：./bin/zookeeper-server-start.sh -daemon ./config/zookeeper.properties
./bin/zookeeper-server-start.sh -daemon ./config/zookeeper.properties
?(2) 開啟kafka(如果內(nèi)存不夠，可以增加虛擬內(nèi)存來實(shí)現(xiàn)或物理內(nèi)存）
前臺(tái)運(yùn)行(顯示Kafka內(nèi)部打印或異常信息)：./bin/kafka-server-start.sh config/server.properties
./bin/kafka-server-start.sh config/server.properties
后臺(tái)運(yùn)行：./bin/kafka-server-start.sh -daemon ./config/server.properties
./bin/kafka-server-start.sh -daemon ./config/server.properties
使用jps命令查看是否正常了
jps
10978 QuorumPeerMain
31613 ConsoleConsumer
31150 Kafka
41839 Jps
三 測(cè)試驗(yàn)證kafka生產(chǎn)和消費(fèi)功能 (3)創(chuàng)建kafka主題：
topic為test
./bin/kafka-topics.sh --create --zookeeper 127.0.0.1:2181 --replication-factor 1 --partitions 1 --topic test
?
#也可以使用下面命令 與上面命令等效
./bin/kafka-topics.sh --create --zookeeper web:2181 --replication-factor 1 --partitions 1 --topic test
其中zookeeper 可以使用hostname 也可以使用IP,若使用hostname,請(qǐng)注意hosts 即/etc/hosts 與hostname最好保持一致!
./bin/kafka-topics.sh --create --zookeeper 127.0.0.1:2181 --replication-factor 1 --partitions 1 --topic test
(4)顯示kafka所有主題：
./bin/kafka-topics.sh --list --zookeeper 192.168.118.128:2181
#也可以使用下面命令 與上面命令等效
./bin/kafka-topics.sh --list --zookeeper web:2181
./bin/kafka-topics.sh --list --zookeeper 127.0.0.1:2181
?
?./bin/kafka-topics.sh --list --zookeeper 192.168.118.128:2181
__consumer_offsets
test
test1
test2
?
?(5)查看某個(gè)主題的詳細(xì)信息：
./bin/kafka-topics.sh --zookeeper 192.168.118.128:2181 --describe ?--topic test2
?
?
Topic: test2?? ?PartitionCount: 2?? ?ReplicationFactor: 1?? ?Configs:?
?? ?Topic: test2?? ?Partition: 0?? ?Leader: 0?? ?Replicas: 0?? ?Isr: 0
?? ?Topic: test2?? ?Partition: 1?? ?Leader: 0?? ?Replicas: 0?? ?Isr: 0
(6)創(chuàng)建kafka生產(chǎn)者：
./bin/kafka-console-producer.sh --broker-list 192.168.118.128:9092 --topic test2
(7)創(chuàng)建kafka消費(fèi)者?
./bin/kafka-console-consumer.sh --bootstrap-server 192.168.118.128:9092 --topic test2 --from-beginning
--from-beginning 是從頭開始消費(fèi)?
如下圖所示:
解釋：
--zookeeper：后面接的是你配置的zookeeper地址
--broker-list:默認(rèn)端口為9092.可自行更改文章來源：http://www.zghlxwxcb.cn/news/detail-610133.html
————————————————
版權(quán)聲明：本文為CSDN博主「樹下水月」的原創(chuàng)文章，遵循CC 4.0 BY-SA版權(quán)協(xié)議，轉(zhuǎn)載請(qǐng)附上原文出處鏈接及本聲明。
原文鏈接：https://blog.csdn.net/u013416034/article/details/123875299文章來源地址http://www.zghlxwxcb.cn/news/detail-610133.html
到了這里，關(guān)于Kafka單機(jī)版部署說細(xì)教程的文章就介紹完了。如果您還想了解更多內(nèi)容，請(qǐng)?jiān)谟疑辖撬阉鱐OY模板網(wǎng)以前的文章或繼續(xù)瀏覽下面的相關(guān)文章，希望大家以后多多支持TOY模板網(wǎng)！
