首先搭建zookeeper集羣:
拷貝zoo_sample.cfg爲zoo.cfg(啓動時會默認調用這個文件)
zoo.cfg
# 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=/var/zoodata
# 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
#添加下面:記住,這裏server.0後面要跟你在ip裏寫的myid一致。而且樓主從0開始才正確。改成1，2，3不正確
server.0=172.18.12.1:2888:3888
server.1=172.18.12.2:2888:3888
server.2=172.18.12.4:2888:3888
因爲我在配置裏指定的/var/zoodata
所以分別在三臺機子的/var/zoodata/myid裏寫入對應的值 :0,1,2.
echo 1 >> /var/zoodata/myid
pg:筆者是用docker映射的本機zookeeper文件。在本機可以。在docker裏會報啓動錯誤。在網上看到有人用高版本報這個錯。所以筆者改用3.4.9.啓動正確。
./zkServer.sh start啓動
啓動之後。運行
./zkServer.sh status
會看到:
Mode: follower或header.zookeeper集羣配置成功.
然後開始配置kafka集羣:
配置文件如下:
# 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
#listeners=PLAINTEXT://:9093
#listeners=PLAINTEXT://:9094
# 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=/var/soft/klogs/kafka-logs-0
#log.dirs=/var/soft/klogs/kafka-logs-1
#log.dirs=/var/soft/klogs/kafka-logs-2
# 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
############################# 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=172.18.12.1:2181,172.18.12.2:2181,172.18.12.4: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
然後啓動:
bin/kafka-server-start.sh -daemon config/server-0.properties
bin/kafka-server-start.sh -daemon config/server-1.properties
bin/kafka-server-start.sh -daemon config/server-2.properties
創建主題:
bin/kafka-topics.sh --create --zookeeper 172.18.12.1:2181,172.18.12.2:2181,172.18.12.4:2181 --replication-factor 3 --partitions 3 --topic testNew
bin/kafka-topics.sh --describe --zookeeper 172.18.12.4:2181 --topic testNew
結果:
Topic: testNew PartitionCount: 3 ReplicationFactor: 3 Configs:
Topic: testNew Partition: 0 Leader: 2 Replicas: 2,0,1 Isr: 2,1
Topic: testNew Partition: 1 Leader: 0 Replicas: 0,1,2 Isr: 0,1,2
Topic: testNew Partition: 2 Leader: 1 Replicas: 1,2,0 Isr: 1,2
[root@9092 kafka_2.11-2.4.0]#
附相關命令:
docker run -e TZ="Asia/Shanghai" --privileged -itd -h 9092.com -p 9092:9092 -v D:\soft:/var/soft --name 9092 --network=mynet --ip 172.18.12.1 test/kaf:v1 /usr/sbin/init
docker exec -it 9092 /bin/bash
docker run -e TZ="Asia/Shanghai" --privileged -itd -h 9093.com -p 9093:9093 -v D:\soft:/var/soft --name 9093 --network=mynet --ip 172.18.12.2 test/kaf:v1 /usr/sbin/init
docker exec -it 9093 /bin/bash
docker run -e TZ="Asia/Shanghai" --privileged -itd -h 9094.com -p 9094:9094 -v D:\soft:/var/soft --name 9094 --network=mynet --ip 172.18.12.4 test/kaf:v1 /usr/sbin/init
docker exec -it 9094 /bin/bash
bin/kafka-server-start.sh -daemon config/server-0.properties
bin/kafka-server-start.sh -daemon config/server-1.properties
bin/kafka-server-start.sh -daemon config/server-2.properties
bin/kafka-topics.sh --create --zookeeper 172.18.12.1:2181 --replication-factor 3 --partitions 1 --topic test-topic
bin/kafka-topics.sh --create --zookeeper 172.18.12.1:2181 --replication-factor 3 --partitions 1 --topic test-topic5
bin/kafka-topics.sh --create --zookeeper 172.18.12.1:2181 --replication-factor 3 --partitions 1 --topic test-topic
bin/kafka-topics.sh --describe --zookeeper 172.18.12.1:2181 --topic test-topic
bin/kafka-topics.sh --describe --zookeeper 172.18.12.4:2181 --topic test-topic
bin/kafka-server-start.sh config/server-1.properties
bin/kafka-server-stop.sh
bin/kafka-topics.sh --create --zookeeper localhost:2181 --replication-factor 3 --partitions 1 --topic my-replicated-topic3
bin/kafka-topics.sh --describe --zookeeper localhost:2181 --topic test-topic
/var/soft/zookeeper-3.4.9/zookeeper-3.4.9/bin/zkServer.sh status
bin/kafka-topics.sh --create --zookeeper 172.18.12.1:2181,172.18.12.2:2181,172.18.12.4:2181 --replication-factor 3 --partitions 1 --topic testNew-1
bin/kafka-topics.sh --describe --zookeeper 172.18.12.4:2181 --topic testNew-1
測試:
創建:
bin/kafka-console-producer.sh --broker-list 172.18.12.1:9092,172.18.12.2:9092,172.18.12.4:9092 --topic topictest
獲取:
bin/kafka-console-consumer.sh --bootstrap-server 172.18.12.1:9092 --topic topictest --from-beginning
參考鏈接:
https://www.jianshu.com/p/bdd9608df6b3
