kafka集群搭建(使用外部zookeeper集群环境方式)

版权声明:本文为博主原创文章,未经博主允许不得转载。 https://blog.csdn.net/m0_37590135/article/details/74078885

前   言

 kafka集群搭建,没有太多可以说的东西,几乎就是照葫芦画瓢。有什么地方不懂或是报错,可以评论,博主会做些修改,若有急需解决问题的,也可直接联系博主,不忙的情况下,博主帮忙解决



环境说明

        工具:

                虚拟机         vmware

                操作系统     红帽7(red hat 7)

                zookeeper  3.4.5

                kafka          0.9

      环境拟定:三节点,主机分别叫node1,node2,node3,ip分别对应:192.168.163.131、192.168.163.130、192.168.163..132




1、下载

博主也是从别人那拿过来的,稍后博主会上传连接给出下载地址。

kafka的0.9版本。








2、安装

 安装没什么好说的,tar -zxvf 文件名,解压归档就完事,然而还是上个图。





3、配置文件配置

3.1、基于OS的环境配置

为了简化后续操作,建议把安装目录下的bin目录放进path里面。
[root@node1 bin]# vi /etc/profile







3.2、外部zookeeper集群安装以及启动

在我的另一篇文章有讲解:http://blog.csdn.net/m0_37590135/article/details/74072472










3.3、kafka配置

${kafka_home}/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=1

############################# Socket Server Settings #############################

listeners=PLAINTEXT://192.168.163.131:9092

# The port the socket server listens on
port=9092

# Hostname the broker will bind to. If not set, the server will bind to all interfaces
host.name=localhost

# Hostname the broker will advertise to producers and consumers. If not set, it uses the
# value for "host.name" if configured.  Otherwise, it will use the value returned from
# java.net.InetAddress.getCanonicalHostName().
#advertised.host.name=<hostname routable by clients>

# The port to publish to ZooKeeper for clients to use. If this is not set,
# it will publish the same port that the broker binds to.
#advertised.port=<port accessible by clients>

# 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=/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=3

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

default.replication.factor=3

# 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=192.168.163.130:2181,192.168.163.131:2181,192.168.163.132:2181

# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=6000
====================================================================================================================================
解析:
        1、使用默认配置就好,注意五个个选项,brokerid、num.partitions、default.replication.factor、zookeeper.connect、zookeeper.connection.timeout.ms
        2、brokerid,当前节点的id号,唯一标识,建议给顺序数字,方便管理
        3、num.partitions,控制设定几个分区,default.replication.factor,控制设定几个备份。
        这里博主有三个节点,所以各给了3。同学们也可根据自身实际情况以及自身需求给定
        4、zookeeper.connect指定外部zk源的各个节点。若无特殊指定,外部zk集群默认端口2181
        5、zookeeper.connection.timeout.ms根据自身网络情况设定,通常默认就好
====================================================================================================================================










3.4将配置好的一份server.properties分发给各个节点

记得修改brokerid选项。








4、启动

各个节点均启动
kafka-server-start.sh /usr/local/kafka_2.11-0.9.0.1/config/server.properties > /usr/local/kafka_2.11-0.9.0.1/logs/logs & //启动线程并写入日志



返回进程号,即开启进程,详细信息给进入自定义的日志路径内查看








5、验证

思路:以下给出几条kafka指令。创建一个topic,一个节点作为生产者,两个节点作为消费者分别看看能否接收数据,进行验证


创建及查看topic
kafka-topics.sh -list -zookeeper 192.168.163.130:2181,192.168.163.131:2181,192.168.163.132:2181    查看所有topic
kafka-topics.sh --create --zookeeper 192.168.163.130:2181,192.168.163.131:2181,192.168.163.132:2181 --replication-factor 3 --partitions 3 --topic xxx (rf参数副本数,par参数分区数,xxx是topic的名称)创建topic


开启生产者以及消费者
kafka-console-producer.sh --broker-list 192.168.163.130:9092,192.168.163.131:9092,192.168.163.132:9092 --topic test 生产者
kafka-console-consumer.sh --zookeeper 192.168.163.130:2181,192.168.163.131:2181,192.168.163.132:2181 --topic test --from-beginning  消费者


如图,是博主之前建立的topic



node1开启生产者:


node2、node3开启消费者,查看队列:







消费者均收到生产者消息,即为成功,这里博主之前的消息未清理,其他多余消息请忽略















6、常见问题解决

6.1、问题描述,启动过一次以后,修改brokerID,再启动,无法成功

        这是由于kafka日志系统无法写入导致的,每次写入日志文件时候,会在日志文件同目录下,生成相关几个文件。其中meta.properties会记录之前brokerID,若是再启动,日志会与kafka的brokerID进行比对,若是一致才准许写入指定的log文件,若是不一致则报错,线程停止






博文不仅仅是防止知识点忘记,也是回馈众多作者们的教导,以此回馈社会

没有更多推荐了,返回首页