zookeeper以及kafka单机安装小结

一时失言乱红尘 2022-02-12 11:11 308阅读 0赞

在一台机器上单机安装kafka记录

## 一、环境配置 ##

kafka 版本 2.11  
Kafka官网下载地址  
JDK版本：1.8  
Zookeeper

# 二、操作过程 #

## 1、下载zookeeper和Kafka并解压 ##

## 2、配置zookeeper ##

zookeeper的安装，这里演示的是单机版的。  
安装参考：  
[https://blog.csdn.net/qq\_27739989/article/details/78078431][https_blog.csdn.net_qq_27739989_article_details_78078431]  
[https://blog.csdn.net/dongdong9223/article/details/81349965][https_blog.csdn.net_dongdong9223_article_details_81349965]

## 3、Kafka解压后目录介绍 ##

/bin 操作kafka的可执行脚本，还包含windows下脚本  
/config 配置文件所在目录  
/libs 依赖库目录  
/logs 日志数据目录，目录kafka把server端日志分为5种类型，分为:server,request,state，log-cleaner，controller

## 4.配置kafka ##

安装很简单，直接将下载的kafka软件的包解压即可，然后配置一下config下面的server.properties文件，主要是修改log路径以及zookeeper的监听地址。然后运行bin下面的kafka-server-start.sh即可。

**配置信息：**

[root@xiehao1 config]# vi 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=PLAINTEXT://:9092
    port=9092
    host.name=127.0.0.1
    #依据具体的服务器，配置相应的服务器的IP地址即可。
    # 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 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=127.0.0.1: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服务**：

[root@localhost bin]# nohup ./kafka-server-start.sh ../config/server.properties &

**单机版的kafka测试，可以多打开几个会话窗口进行topic测试功能完备性**  
启动2个XSHELL客户端，一个用于生产者producer发送消息，一个用于消费者consumer接受消息。  
**运行producer，随机敲入几个字符，相当于把这个敲入的字符消息发送给队列。**

[root@xiehao1 bin]# ./kafka-console-producer.sh --broker-list 127.0.0.1:9092 --top test
    >12
    >天才                             
    >人

**运行consumer，可以看到刚才发送的消息列表。**

[root@xiehao1 bin]# ./kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9092 --topic test --from-beginning
    12
    12
    天才
    人才

## 三、报错记录： ##

\***启动服务遇见的错误-1：**  
kafka启动时报错：java.net.UnknownHostException: Name or service not known  
解决方法：  
1.打开/etc/hosts文件，加上ip和主机名

[root@xiehao1 etc]# vi /etc/hosts
    127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
    ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
    192.168.197.129 xiehao1 localhost
    ~

启动ok\*

\***启动消费者时遇见的错误 -2：**  
无法接受消息  
是kafka的server.properties的配置错误。主要是下面的内容配置有问题：

listeners=PLAINTEXT://:9092

将这句注释掉，然后在配置文件中添加下面的两行配置，指明当前broker的地址：

port=9092
    host.name=10.90.7.2 #依据具体的服务器，配置相应的服务器的IP地址即可。

\*\*  
修改后，再次**重启**kafka服务，重新在某台服务器上启动消息生产者服务。\*

[https_blog.csdn.net_qq_27739989_article_details_78078431]: https://blog.csdn.net/qq_27739989/article/details/78078431
[https_blog.csdn.net_dongdong9223_article_details_81349965]: https://blog.csdn.net/dongdong9223/article/details/81349965