部署Zookeeper

节点信息

节点 IP
elastic-01 10.0.0.51
elastic-02 10.0.0.52
elastic-03 10.0.0.53

安装Zookeeper

将kafka的安装包下载至本地，并分别上传至上面三台服务器
1、解压并重命名，三个节点分别执行
[root@elastic-01 ~]# tar -zxvf kafka_2.13-2.8.0.tgz -C /usr/local/
[root@elastic-01 ~]# mv kafka_2.13-2.8.0 kafka
2、修改zookeeper配置文件,将如下配置文件依次copy到另外两个节点
[root@elastic-01 ~]# vim /usr/local/kafka/config/zookeeper.properties

  1. dataDir=/opt/data/zookeeper/data
  2. dataLogDir=/opt/data/zookeeper/logs
  3. clientPort=2181
  4. tickTime=2000
  5. initLimit=20
  6. syncLimit=10
  7. server.1=10.0.0.51:2888:3888
  8. server.2=10.0.0.52:2888:3888
  9. server.3=10.0.0.53:2888:3888

配置项含义∶

  • dataDir zk数据存放目录
  • dataLogDir zK日志存放目录
  • clientPort 客户端连接zK服务的端口
  • tickTime zK服务器之间或客户端与服务器之间维持心跳的时间间隔。
  • initLimit 允许follower连接并同步到Leader的初始化连接时间，当初始化连接时间超过该值，则表示连接失败
  • syncLimit Leader与Follower之间发送消息时如果follower在设置时间内不能与leader通信，那么此follower将会被丢弃
  • server.1=10.0.0.51:2888:3888 2888是follower与leader交换信息的端口，3888是当leader挂了时用来执行选举时服务器相互通信的端口

3、创建工作目录,三个节点分别执行
[root@elastic-01 ~]# mkdir -p /opt/data/zookeeper/{data,logs}
4、输入集群id
[root@elastic-01 ~]# echo 1 /opt/data/zookeeper/data/myid
[root@elastic-02 ~]# echo 2 /opt/data/zookeeper/data/myid
[root@elastic-03 ~]# echo 3 /opt/data/zookeeper/data/myid

启动Zookeeper

切换到/usr/local/kafka目录，并在三个节点分别执行如下启动命令
[root@elastic-01 kafka]# nohup bin/zookeeper-server-start.sh config/zookeeper.properties &

部署Kafka

安装Kafka

1、修改配置，并将此配置文件copy到另外两个节点，同时对broker.id和listeners字段做对应的修改

  1. [root@elastic-01 config]# cat server.properties 
  2. # Licensed to the Apache Software Foundation (ASF) under one or more
  3. # contributor license agreements.  See the NOTICE file distributed with
  4. # this work for additional information regarding copyright ownership.
  5. # The ASF licenses this file to You under the Apache License, Version 2.0
  6. # (the "License"); you may not use this file except in compliance with
  7. # the License.  You may obtain a copy of the License at
  8. #
  9. #    http://www.apache.org/licenses/LICENSE-2.0
  10. #
  11. # Unless required by applicable law or agreed to in writing, software
  12. # distributed under the License is distributed on an "AS IS" BASIS,
  13. # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  14. # See the License for the specific language governing permissions and
  15. # limitations under the License.
  17. # see kafka.server.KafkaConfig for additional details and defaults
  19. ############################# Server Basics #############################
  21. # The id of the broker. This must be set to a unique integer for each broker.
  22. broker.id=1
  24. ############################# Socket Server Settings #############################
  26. # The address the socket server listens on. It will get the value returned from 
  27. # java.net.InetAddress.getCanonicalHostName() if not configured.
  28. #   FORMAT:
  29. #     listeners = listener_name://host_name:port
  30. #   EXAMPLE:
  31. #     listeners = PLAINTEXT://your.host.name:9092
  32. listeners=PLAINTEXT://10.0.0.51:9092
  34. # Hostname and port the broker will advertise to producers and consumers. If not set, 
  35. # it uses the value for "listeners" if configured.  Otherwise, it will use the value
  36. # returned from java.net.InetAddress.getCanonicalHostName().
  37. #advertised.listeners=PLAINTEXT://your.host.name:9092
  39. # Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
  40. #listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL
  42. # The number of threads that the server uses for receiving requests from the network and sending responses to the network
  43. num.network.threads=3
  45. # The number of threads that the server uses for processing requests, which may include disk I/O
  46. num.io.threads=8
  48. # The send buffer (SO_SNDBUF) used by the socket server
  49. socket.send.buffer.bytes=102400
  51. # The receive buffer (SO_RCVBUF) used by the socket server
  52. socket.receive.buffer.bytes=102400
  54. # The maximum size of a request that the socket server will accept (protection against OOM)
  55. socket.request.max.bytes=104857600
  58. ############################# Log Basics #############################
  60. # A comma separated list of directories under which to store log files
  61. log.dirs=/opt/data/kafka/logs
  63. # The default number of log partitions per topic. More partitions allow greater
  64. # parallelism for consumption, but this will also result in more files across
  65. # the brokers.
  66. num.partitions=6
  68. # The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
  69. # This value is recommended to be increased for installations with data dirs located in RAID array.
  70. num.recovery.threads.per.data.dir=1
  72. ############################# Internal Topic Settings  #############################
  73. # The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
  74. # For anything other than development testing, a value greater than 1 is recommended to ensure availability such as 3.
  75. offsets.topic.replication.factor=2
  76. transaction.state.log.replication.factor=1
  77. transaction.state.log.min.isr=1
  79. ############################# Log Flush Policy #############################
  81. # Messages are immediately written to the filesystem but by default we only fsync() to sync
  82. # the OS cache lazily. The following configurations control the flush of data to disk.
  83. # There are a few important trade-offs here:
  84. #    1. Durability: Unflushed data may be lost if you are not using replication.
  85. #    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.
  86. #    3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks.
  87. # The settings below allow one to configure the flush policy to flush data after a period of time or
  88. # every N messages (or both). This can be done globally and overridden on a per-topic basis.
  90. # The number of messages to accept before forcing a flush of data to disk
  91. #log.flush.interval.messages=10000
  93. # The maximum amount of time a message can sit in a log before we force a flush
  94. #log.flush.interval.ms=1000
  96. ############################# Log Retention Policy #############################
  98. # The following configurations control the disposal of log segments. The policy can
  99. # be set to delete segments after a period of time, or after a given size has accumulated.
  100. # A segment will be deleted whenever *either* of these criteria are met. Deletion always happens
  101. # from the end of the log.
  103. # The minimum age of a log file to be eligible for deletion due to age
  104. log.retention.hours=168
  106. # A size-based retention policy for logs. Segments are pruned from the log unless the remaining
  107. # segments drop below log.retention.bytes. Functions independently of log.retention.hours.
  108. #log.retention.bytes=1073741824
  110. # The maximum size of a log segment file. When this size is reached a new log segment will be created.
  111. log.segment.bytes=1073741824
  113. # The interval at which log segments are checked to see if they can be deleted according
  114. # to the retention policies
  115. log.retention.check.interval.ms=300000
  117. ############################# Zookeeper #############################
  119. # Zookeeper connection string (see zookeeper docs for details).
  120. # This is a comma separated host:port pairs, each corresponding to a zk
  121. # server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
  122. # You can also append an optional chroot string to the urls to specify the
  123. # root directory for all kafka znodes.
  124. zookeeper.connect=10.0.0.51:2181,10.0.0.52:2181,10.0.0.53:2181
  126. # Timeout in ms for connecting to zookeeper
  127. zookeeper.connection.timeout.ms=6000
  130. ############################# Group Coordinator Settings #############################
  132. # The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
  133. # 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.
  134. # The default value for this is 3 seconds.
  135. # We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
  136. # 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.
  137. group.initial.rebalance.delay.ms=0

字段解释

  • listeners=PLAINTEXT://192.168.19.22:9092监听地址
  • num.network.threads broker处理消息的最大线程数，一般情况下不需要去修改
  • num.io.threads broker处理磁盘Io的线程数，数值应该大于你的硬盘数
  • socket.send.buffer.bytes socket的发送缓冲区
  • socket.receive.buffer.bytes socket的接收缓冲区
  • socket.request.max.bytes socket请求的最大数值，防止server OOM
  • log.dirs 日志文件目录
  • num.partitions
  • num.recovery.threads.per.data.dir
  • offsets.topic.replication.factor
  • log.cleanup.policy = delete 日志清理策略选择有: delete和compact主要针对过期数据的处理，或是日志文件达到限制的额度，会被topic创建时的指定参数覆盖

2、创建工作目录
[root@elastic-01 ~]# mkdir -p /opt/data/kafka/logs

启动Kafka

切换到/usr/local/kafka目录，分别在三个节点依次执行如下启动命令
[root@elastic-01 ~]# nohup bin/kafka-server-start.sh config/server.properties &

测试

备注：Kafka 从 2.2 版本开始将 kafka-topic.sh 脚本中的 −−zookeeper 参数标注为 “过时”，推荐使用 −−bootstrap-server 参数。注意两个参数指向的地址是不同的
1、在kafka集群创建一个topic主题，并模拟消息的产生者生产数据

  1. [root@elastic-01 kafka]#  ./kafka-topics.sh --create --bootstrap-server 10.0.0.51:9092,10.0.0.52:9092,10.0.0.53:9092 --replication-factor 2 --partitions 2 --topic mytest-topic
  2. Created topic mytest-topic.
  3. [root@elastic-01 kafka]#  ./kafka-console-producer.sh --bootstrap-server 10.0.0.51:9092,10.0.0.52:9092,10.0.0.93:9092 --topic mytest-topic
  4. >xiang      
  5. >shi
  6. >chauan

2、查看kafka集群上已有的topic

  1. [root@elastic-01 kafka]# bin/kafka-topics.sh --bootstrap-server 10.0.0.51:9092,10.0.0.52:9092,10.0.0.53:9092 --list
  2. __consumer_offsets
  3. cce-test-topic
  4. mytest-topic

3、在另外一个节点上模拟数据的消费端，消费数据，可以看到消费端收到了有生产者产生的数据，说明kafka集群是正常的

  1. [root@elastic-03 kafka]# ./kafka-console-consumer.sh --bootstrap-server 10.0.0.51:9092,10.0.0.52:9092,10.0.0.93:9092 --topic  mytest-topic
  2. xiang
  3. shi
  4. chauan