共计 6797 个字符,预计需要花费 17 分钟才能阅读完成。
虚拟机三台 192.168.1.133;192.168.1.134;192.168.1.135
启动顺序首先启动 Zookeeper 集群, 再启动 Kafka 集群
一、Zookeeper:
1、找到解压目录下的 conf 文件夹, 在该文件夹下新建 zoo.cfg 文件, 并且将一下配置写入(三台 Zookeeper 配置文件 zoo.cfg 内容相同)
zoo.cfg
tickTime=2000 | |
initLimit=10 | |
syncLimit=5 | |
dataDir=/opt/zookeeper-3.4.10/data | |
dataLogDir=/opt/zookeeper-3.4.10/logs | |
clientPort=2181 | |
server.1=192.168.1.133:3888:4888 | |
server.2=192.168.1.134:3888:4888 | |
server.3=192.168.1.135:3888:4888 |
2、在解压目录下新建 data 文件夹, 并在 data 文件夹内新建 myid 文件, 并写入 1(192.168.1.134 写入 2;192.168.1.135, 写入 3)
3、在解压目录下新建 logs 文件夹
二、Kafka:
找到解压目录下的 config 文件夹, 只需要修改其中的 server.properties 文件, 其他配置文件不需要修改
server.properties(192.168.1.133)
# 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=192.168.1.133 | |
port=9092 | |
# 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 = security_protocol://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 | |
# 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=1048576 | |
# The receive buffer (SO_RCVBUF) used by the socket server | |
socket.receive.buffer.bytes=1048576 | |
# 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=/KafkaLogs | |
# 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 | |
log.retention.hours=168 | |
message.max.byte=5048576 | |
default.replication.factor=3 | |
replica.fetch.max.byte=5048576 | |
# 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 | |
# 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.1.133:2181,192.168.1.134:2181,192.168.1.135:2181 | |
# Timeout in ms for connecting to zookeeper | |
zookeeper.connection.timeout.ms=6000 |
192.168.1.134 修改:
broker.id=2 | |
host.name=192.168.1.134 | |
port=9092配置其他不变 |
192.168.1.135 修改:
broker.id=3host.name=192.168.1.134 | |
port=9092配置其他不变 |
三、启动 1、启动三台 Zookeeper:/zookeeper-3.4.10//bin/zkServer.sh start 启动/zookeeper-3.4.10//bin/zkServer.sh status 查看状态2、启动三台 Kafka:/kafka_2.11-0.10.1.1/bin/kafka-server-start.sh -daemon /kafka_2.11-0.10.1.1/config/server.properties 修改示例 可以到 Linux 公社资源站下载:
—————————————— 分割线 ——————————————
免费下载地址在 http://linux.linuxidc.com/
用户名与密码都是www.linuxidc.com
具体下载目录在 /2017 年资料 /12 月 /11 日 /Kafka 集群搭建示例 /
下载方法见 http://www.linuxidc.com/Linux/2013-07/87684.htm
—————————————— 分割线 ——————————————
下面关于 Kafka 的文章您也可能喜欢,不妨参考下:
CentOS 7.2 部署 Elasticsearch+Kibana+Zookeeper+Kafka http://www.linuxidc.com/Linux/2016-11/137636.htm
CentOS 7 下安装 Logstash ELK Stack 日志管理系统 http://www.linuxidc.com/Linux/2016-08/134165.htm
Kafka 集群部署与配置手册 http://www.linuxidc.com/Linux/2017-02/141037.htm
CentOS 7 下 Kafka 集群安装 http://www.linuxidc.com/Linux/2017-01/139734.htm
Apache Kafka 教程笔记 http://www.linuxidc.com/Linux/2014-01/94682.htm
CentOS 7 下安装 Kafka 单机版 http://www.linuxidc.com/Linux/2017-01/139732.htm
Apache kafka 原理与特性(0.8V) http://www.linuxidc.com/Linux/2014-09/107388.htm
Kafka 部署与代码实例 http://www.linuxidc.com/Linux/2014-09/107387.htm
Kafka 介绍及环境搭建 http://www.linuxidc.com/Linux/2016-12/138724.htm
Kafka 介绍和集群环境搭建 http://www.linuxidc.com/Linux/2014-09/107382.htm
CentOS7.0 安装配置 Kafka 集群 http://www.linuxidc.com/Linux/2017-06/144951.htm
Kafka 的详细介绍:请点这里
Kafka 的下载地址:请点这里
本文永久更新链接地址:http://www.linuxidc.com/Linux/2017-12/149321.htm
