Window系统下搭建Zookeeper和Kafka环境

你的名字 2022-05-09 02:38 270阅读 0赞

## 一.准备工具 ##

*  JDK 1.8 (此环境就不赘述,自行百度下载搭建)
 *  Zookeeper安装包([下载][Link 1])
 *  Kafka安装包([下载][Link 2])

## 二.安装Zookeeper ##

1.  下载好压缩包后,解压到本地磁盘,此处的解压路径为D:\\KafkaTool\\zookeeper-3.4.12
2.  打开路径D:\\KafkaTool\\zookeeper-3.4.12\\conf下的zoo\_sample.cfg,为了方便管理,将该文件重命名为zoo.cfg
3.  修改dataDir保存路径.用文本编辑器打开zoo.cfg,将dataDir=/tmp/zookeeper改成dataDir=D:\\\\KafkaTool\\\\zookeeper-3.4.12\\\\tmp(此处是本人的配置,读者根据个人实际安装路径配置).该文件修改后如下所示:
    
        # The number of milliseconds of each tick
        tickTime=2000
        # The number of ticks that the initial 
        # synchronization phase can take
        initLimit=10
        # The number of ticks that can pass between 
        # sending a request and getting an acknowledgement
        syncLimit=5
        # the directory where the snapshot is stored.
        # do not use /tmp for storage, /tmp here is just 
        # example sakes.
        dataDir=D:\\KafkaTool\\zookeeper-3.4.12\\tmp
        # 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
        #autopurge.snapRetainCount=3
        # Purge task interval in hours
        # Set to "0" to disable auto purge feature
        #autopurge.purgeInterval=1
4.  系统变量中添加ZOOKEEPER\_HOME=D:\\KafkaTool\\zookeeper-3.4.12,编辑系统变量中的path变量，增加%ZOOKEEPER\_HOME%\\bin
5.  在zoo.cfg文件中修改默认的Zookeeper端口(默认端口2181)
6.  打开cmd窗口，输入zkserver，运行Zookeeper，运行结果如下：![70][]

如果输入zkserver命令,出现以上界面,说明Zookeeper已经安装完成，已在2181端口运行

## 三.安装Kafka ##

1.解压已下载好的Kafka安装包,此处的解压路径为D:\\KafkaTool\\kafka\_2.10-0.10.2.1

2.用文本编辑器打开D:\\KafkaTool\\kafka\_2.10-0.10.2.1\\config目录下的server.properties文件,将其内容中的log.dirs=/tmp/kafka-logs改成log.dirs=D:\\\\KafkaTool\\\\kafka\_2.10-0.10.2.1\\\\kafka-logs.其修改后的内容如下所示:

# 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
    
    # 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 = 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 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=D:\\KafkaTool\\kafka_2.10-0.10.2.1\\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
    
    ############################# 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
    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. 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=6000

3.此时就可以运行Kafka了.进入Kafka的安装目录D:\\KafkaTool\\kafka\_2.10-0.10.2.1,在空白处按下shift+鼠标右键,选择"在此处打开命令窗口"，打开命令行.在命令行中输入：**.\\bin\\windows\\kafka-server-start.bat .\\config\\server.properties** 回车。如下图所示:

![70 1][]

正确运行的情况如下:

![70 2][]

**此时zookeeper以及kafka都已正确运行.**

## **四.测试使用Kafka的消息机制功能** ##

1.创建主题**topics**

进入D:\\KafkaTool\\kafka\_2.10-0.10.2.1\\bin\\windows文件夹,在空白处按下shift+鼠标右键,选择"在此处打开命令窗口"，打开命令行,输入命令: **kafka-topics.bat --create --zookeeper localhost:2181 --replication-factor 1 --partitions 1 --topic haige**

**![70 3][]**

**2.**创建生产者**producer**

进入D:\\KafkaTool\\kafka\_2.10-0.10.2.1\\bin\\windows文件夹,在空白处按下shift+鼠标右键,选择"在此处打开命令窗口"，打开命令行,输入命令: **kafka-console-producer.bat --broker-list localhost:9092 --topic haige**

**![70 4][]**

3.创建消费者**consumer**

进入D:\\KafkaTool\\kafka\_2.10-0.10.2.1\\bin\\windows文件夹,在空白处按下shift+鼠标右键,选择"在此处打开命令窗口"，打开命令行,输入命令: **kafka-console-consumer.bat --zookeeper localhost:2181 --topic haige**

**![70 5][]**

注意在运行过程中,不要关闭以上窗口.就可以在生产者**producer**控制台窗口输入消息了。在消息输入过后，很快消费者**Consumer**窗口就会显示出**Producer**发送的消息

[Link 1]: https://download.csdn.net/download/linhaiyun_ytdx/10692036
[Link 2]: https://download.csdn.net/download/linhaiyun_ytdx/10696571
[70]: /images/20220509/002c29e5e50844b89206f79a1a138bf0.png
[70 1]: /images/20220509/7235f9d4811a465fb21ed18787694da0.png
[70 2]: /images/20220509/369991d68335467c906a07dc1be3b95b.png
[70 3]: /images/20220509/6e8b94b5db2e401e99c6ba4fbda47b05.png
[70 4]: /images/20220509/c14dfb04d2ba484cbbaf87db966f7f3f.png
[70 5]: /images/20220509/bea853a884f94c44902ff54afe125d2a.png