Zookeeper+Kafka集群部署
kafka: kafka_2.11-2.2.0.tar.gz
zookeeper: zookeeper-3.4.10.tar.gz
主机规划
192.168.xxx.94 Kafka+ZooKeeper
192.168.xxx.97 Kafka+ZooKeeper
192.168.xxx.100 Kafka+ZooKeeper
192.168.xxx.103 kafka
软件下载地址:
zookeeper: http://archive.apache.org/dist/zookeeper/zookeeper-3.4.10/
kafka: http://kafka.apache.org/downloads
host文件
cat /etc/hosts
192.168.xxx.94 nginx-94
192.168.xxx.97 nginx-97
192.168.xxx.100 nginx-100
192.168.xxx.103 nginx-103
安装zookeeper
1.解压 tar -zxvf zookeeper-3.4.10.tar.gz
2.修改配置文件
cp zoo_sample.cfg zoo.cfg
[iknow@nginx-100 zookeeper-3.4.10]$ cat conf/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=/tmp/zookeeper
dataDir=/home/iknow/data/zookeeper
# 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.1=192.168.xxx.94:2888:3888
server.2=192.168.xxx.97:2888:3888
server.3=192.168.xxx.100:2888:3888
3.创建dataDir目录 /home/iknow/data/zookeeper
4.将zookeeper文件复制到另外两个节点 略...
5.创建目录/home/iknow/data/zookeeper
echo 1 > /home/iknow/data/zookeeper/myid
[iknow@nginx-97 data]$ cat zookeeper/myid
2
6.分别在每个节点上启动 zookeeper测试：
./bin/zkServer.sh start
启动报错，不能连接到另外的机器，因为是新机器，未做免密码登录
免密码登录
以nginx-100为例
ssh-keygen -t rsa
[iknow@nginx-100 .ssh]$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/iknow/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/iknow/.ssh/id_rsa.
Your public key has been saved in /home/iknow/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:+JuqGruNMQ1FJy1p2DqmqPtdDSLPF77imrlKDO4OMV0 [email protected]
The key's randomart image is:
+---[RSA 2048]----+
| ooo. |
| ..=o. |
| oE. |
| .+o . |
|=o+.. + S |
|*o * o = |
|o++ + + o |
|= @.o . o |
|+*@*=oo.o |
+----[SHA256]-----+
[iknow@owl-nginx-129-100 .ssh]$ ll
total 12
-rw------- 1 iknow iknow 1679 Dec 4 15:43 id_rsa
-rw-r--r-- 1 iknow iknow 421 Dec 4 15:43 id_rsa.pub
-rw-r--r-- 1 iknow iknow 176 Nov 5 20:05 known_hosts
登录自己仍然需要密码
[iknow@owl-nginx-129-100 .ssh]$ ll
total 12
-rw------- 1 iknow iknow 1679 Dec 4 15:43 id_rsa
-rw-r--r-- 1 iknow iknow 421 Dec 4 15:43 id_rsa.pub
-rw-r--r-- 1 iknow iknow 176 Nov 5 20:05 known_hosts
[iknow@owl-nginx-129-100 .ssh]$ touch authorized_keys
[iknow@owl-nginx-129-100 .ssh]$ hostname
owl-nginx-129-100.bjdd.zybang.com
[iknow@owl-nginx-129-100 .ssh]$ ssh owl-nginx-129-100.bjdd.zybang.com
The authenticity of host 'owl-nginx-129-100.bjdd.zybang.com (192.168.129.100)' can't be established.
ECDSA key fingerprint is SHA256:geoHy6CA94pDg50x3+2mjCO5bcqB6qZMMx7NcGJcQTU.
ECDSA key fingerprint is MD5:7e:70:ed:83:3c:66:42:b2:69:dc:17:dd:48:ee:c1:81.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'owl-nginx-129-100.bjdd.zybang.com,192.168.129.100' (ECDSA) to the list of known hosts.
[email protected]'s password:
Permission denied, please try again.
[email protected]'s password:
Permission denied, please try again.
[email protected]'s password:
Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
同样可以看到.ssh目录下没有authorized_keys文件的，创建authorized_keys文件,
追加公钥到authorized_keys
[iknow@owl-nginx-129-100 .ssh]$ ll
total 12
-rw-rw-r-- 1 iknow iknow 0 Dec 4 15:44 authorized_keys
-rw------- 1 iknow iknow 1679 Dec 4 15:43 id_rsa
-rw-r--r-- 1 iknow iknow 421 Dec 4 15:43 id_rsa.pub
-rw-r--r-- 1 iknow iknow 387 Dec 4 15:45 known_hosts
[iknow@owl-nginx-129-100 .ssh]$ cat id_rsa.pub > authorized_keys
[iknow@owl-nginx-129-100 .ssh]$ ll
total 16
-rw-rw-r-- 1 iknow iknow 421 Dec 4 15:46 authorized_keys
-rw------- 1 iknow iknow 1679 Dec 4 15:43 id_rsa
-rw-r--r-- 1 iknow iknow 421 Dec 4 15:43 id_rsa.pub
-rw-r--r-- 1 iknow iknow 387 Dec 4 15:45 known_hosts
修改权限
.ssh目录权限是700，
drwx------ 2 iknow iknow 4096 Feb 21 17:39 .ssh
authorized_keys文件权限是644
[iknow@data-hadoop-50-63 ~]$ ll ~/.ssh/
total 16
-rw-rw-r-- 1 iknow iknow 421 Feb 21 17:40 authorized_keys
将文件权限改为600后，再次登录,发现是可以免密码登录的（免密码登录自己）
[iknow@owl-nginx-129-100 .ssh]$ ll
total 16
-rw------- 1 iknow iknow 421 Dec 4 15:46 authorized_keys
-rw------- 1 iknow iknow 1679 Dec 4 15:43 id_rsa
-rw-r--r-- 1 iknow iknow 421 Dec 4 15:43 id_rsa.pub
-rw-r--r-- 1 iknow iknow 387 Dec 4 15:45 known_hosts
[iknow@owl-nginx-129-100 ~]$ ssh owl-nginx-129-100.bjdd.zybang.com
Last failed login: Wed Dec 4 15:46:26 CST 2019 from owl-nginx-129-100.bjdd.zybang.com on ssh:notty
There were 4 failed login attempts since the last successful login.
Last login: Wed Dec 4 15:26:43 2019 from owl-nginx-129-94.bjdd.zybang.com
查看zookeeper启动日志报错:
[iknow@owl-nginx-129-94 zookeeper-3.4.10]$ cat zookeeper.out
nohup: failed to run command ‘java’: No such file or directory
原因是没有安装jdk，安装jdk，命令如下: yum install java-1.8.0-openjdk* -y
安装之后启动zk
[iknow@nginx-97 zookeeper-3.4.10]$ ./bin/zkServer.sh start
ZooKeeper JMX enabled by default
Using config: /home/iknow/apps/zookeeper-3.4.10/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED
[iknow@owl-nginx-129-97 zookeeper-3.4.10]$ ./bin/zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /home/iknow/apps/zookeeper-3.4.10/bin/../conf/zoo.cfg
Mode: leader
[iknow@nginx-94 zookeeper-3.4.10]$ ./bin/zkServer.sh start
ZooKeeper JMX enabled by default
Using config: /home/iknow/apps/zookeeper-3.4.10/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED
查看启动状态
[iknow@nginx-94 zookeeper-3.4.10]$ ./bin/zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /home/iknow/apps/zookeeper-3.4.10/bin/../conf/zoo.cfg
Mode: follower
[iknow@nginx-100 zookeeper-3.4.10]$ ./bin/zkServer.sh start
ZooKeeper JMX enabled by default
Using config: /home/iknow/apps/zookeeper-3.4.10/bin/../conf/zoo.cfg
Starting zookeeper ... STARTED
[iknow@nginx-100 zookeeper-3.4.10]$ ./bin/zkServer.sh status
ZooKeeper JMX enabled by default
Using config: /home/iknow/apps/zookeeper-3.4.10/bin/../conf/zoo.cfg
Mode: follower
zk正常启动了
安装kafka
1.解压: tar -zxvf kafka_2.11-2.2.0.tar.gz
2.修改server.properties文件
cat config/server.properties
[iknow@nginx-97 kafka_2.11-2.2.0]$ cat 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
# Switch to enable topic deletion or not, default value is false
delete.topic.enable=true
log.cleaner.enable=true
auto.create.topics.enable=false
default.replication.factor=2
############################# 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://nginx-97: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
advertised.listeners=PLAINTEXT://nginx-97: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
num.network.threads=6
# The number of threads that the server uses for processing requests, which may include disk I/O
#num.io.threads=8
num.io.threads=12
# 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
log.dirs=/home/iknow/data/kafka
# 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
num.partitions=4
# 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
log.retention.hours=8
# 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=localhost:2181
zookeeper.connect=192.168.xxx.94:2181,192.168.xxx.97:2181,192.168.xxx.100: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
replica.fetch.max.bytes=20971520
message.max.bytes=10485760
num.replica.fetchers=2
3.将kafka_2.11-2.2.0 文件夹复制到另外三个节点
并修改每个节点对应的 server.properties 文件的 broker.id和listenrs,以其中一个为例:
broker.id=2
#listeners=PLAINTEXT://:9092
listeners=PLAINTEXT://nginx-97: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
advertised.listeners=PLAINTEXT://nginx-97:9092
Zookeeper+Kafka集群测试
创建topic：
[iknow@nginx-94 kafka_2.11-2.2.0]$ ./bin/kafka-topics.sh --create --zookeeper nginx-97:2181, nginx-94:2181, nginx-100:2181 --replication-factor 3 --partitions 3 --topic test
Created topic test.
显示topic:
[iknow@nginx-94 kafka_2.11-2.2.0]$ ./bin/kafka-topics.sh --describe --zookeeper nginx-97:2181, nginx-94:2181, nginx-100:2181 --topic test
Topic:test PartitionCount:3 ReplicationFactor:3 Configs:
Topic: test Partition: 0 Leader: 2 Replicas: 2,1,0 Isr: 2,1,0
Topic: test Partition: 1 Leader: 0 Replicas: 0,2,1 Isr: 0,2,1
Topic: test Partition: 2 Leader: 1 Replicas: 1,0,2 Isr: 1,0,2
broker启动脚本
iknow@data-96:~/apps $ cat kafka_2.11-2.1.0/start.sh
export JMX_PORT=9999
./bin/kafka-server-start.sh -daemon config/server.properties
创建topic脚本
iknow@data-96:~/apps $ cat kafka_2.11-2.1.0/create_topic.sh
topic=$1
bin/kafka-topics.sh \
--zookeeper zk01:2181,zk02:2181,zk03:2181 \
--create --topic $topic \
--partitions 3 \
--replication-factor 2 \
--config max.message.bytes=10485760
参考:
Zookeeper+Kafka集群部署
zookeeper启动报错：nohup: failed to run command ‘java’: No such file or directory