IT评测·应用市场-qidao123.com

标题: Kafka学习之：mac 上安装 kafka [打印本页]

---

作者: 道家人    时间: 2024-7-17 14:55
标题: Kafka学习之：mac 上安装 kafka
Brew 安装

• 打开终端
  

1. xcode-select --install

• 起首要安装这个东西，否则安不了 kafka
  1. xcode-select --install

  复制代码
• 安装完成后，你大概必要同意Xcode和相干工具的允许协议。这可以通过以下命令完成：
  1. sudo xcodebuild -license

  复制代码

2. brew install kafka

• 安装 kafka
  1. brew install kafka

  复制代码

Docker 安装

• 如果你已经安装了Docker，可以使用Docker来运行Kafka和ZooKeeper。
  

1. 构建 docker-compose.yml

• 在终端中创建一个docker-compose.yml文件，内容如下：
  

1. version: '2'
2. services:
3.   zookeeper:
4.     image: wurstmeister/zookeeper
5.     ports:
6.       - "2181:2181"
7.   kafka:
8.     image: wurstmeister/kafka
9.     ports:
10.       - "9092:9092"
11.     environment:
12.       KAFKA_ADVERTISED_HOST_NAME: 127.0.0.1
13.       KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181
14.     volumes:
15.       - /var/run/docker.sock:/var/run/docker.sock

复制代码

docker 文件剖析

zookeeper

   

• 起首通过 services 定义了容器使用的所有服务，由于 kafka 启动必要借助于 zookeeper，所以我们要同时在 docker 容器中具备 kafka 和 zookeeper 两种服务
  

1.   zookeeper:
2.     image: wurstmeister/zookeeper
3.     ports:
4.       - "2181:2181"

复制代码

  

• zookeeper: 这是服务的名称，在这个设置中体现 Zookeeper 服务。
  
• image: 使用的Docker镜像，此处是 wurstmeister/zookeeper。这是一个预设置的 Zookeeper 镜像，适合与Kafka协同工作。
  
• ports:"2181:2181" 将容器内的 2181 端口映射到宿主机的 2181 端口。Zookeeper 默认监听 2181 端口，用于 kafka 客户端毗连。
  

  kafka

1.   kafka:
2.     image: wurstmeister/kafka
3.     ports:
4.       - "9092:9092"
5.     environment:
6.       KAFKA_ADVERTISED_HOST_NAME: 127.0.0.1
7.       KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181
8.     volumes:
9.       - /var/run/docker.sock:/var/run/docker.sock

复制代码

  

• kafka 这是另一个服务，体现Kafka服务器。
  
• image 使用的是 wurstmeister/kafka 镜像，这是一个预设置的Kafka镜像。
  
• ports: "9092:9092" 将容器内的9092端口映射到宿主机的9092端口。Kafka默认监听9092端口，用于客户端毗连。
  
• environment 设置环境变量来设置Kafka。
  
• KAFKA_ADVERTISED_HOST_NAME 告知Kafka怎样将自己广告给客户端。在这里设置为127.0.0.1，意味着Kafka将只能从宿主机本地访问。
  
• KAFKA_ZOOKEEPER_CONNECT 指定Kafka怎样毗连到Zookeeper。zookeeper:2181 体现使用此Docker Compose设置中定义的zookeeper服务及其2181端口。
  
• volumes: /var/run/docker.sock:/var/run/docker.sock 将宿主机的Docker套接字文件挂载到容器中。这答应Kafka容器管理其他Docker容器，通常用于动态创建和管理Kafka集群的Broker。
  

  2. 通过 docker 构建容器并对外提供服务

• 选择适合你的需求的安装方法。安装完成后，你就可以开始使用Kafka进行消息队列的开发和测试了。
  

1. docker-compose up

复制代码

MAC 本机 Kafka 启动（使用 默认设置）

• 起首启动 zookeeper
  

1. brew services start zookeeper

复制代码

• 如果是本地安装的 kafka，则直接可以用下列命令启动，默认情况下Kafka会监听在9092端口上。这个默认举动是由Kafka的设置文件决定的，该设置文件通常位于/usr/local/etc/kafka/server.properties（如果你是通过Homebrew安装的Kafka）而我是 M1 芯片的 macbook，我的默认安装地址是 /opt/homebrew/etc/kafka/server.properties
  

1. brew services start kafka

复制代码

• 如果更改了 server.properties 则必要重新运行 kafka 来生效设置
  

1. brew services restart kafka

复制代码

检测 kafka 是否正确启动

方法1: 使用lsof命令

1. lsof -i :9092

复制代码

• 这个命令会列出所有监听在9092端口的历程。如果Kafka已经启动而且在此端口上监听，你应该能看到它的历程信息。如果这个命令返回了关于Kafka历程的信息，那么就意味着Kafka已经在9092端口上正确启动了。
  

方法 2：使用Kafka命令行工具

• 执行以下命令来创建一个新主题：
  

1. kafka-topics --create --topic test --partitions 1 --replication-factor 1 --bootstrap-server localhost:9092

复制代码

• 如果这个命令成功执行并没有报错，那么就意味着Kafka服务已经在监听9092端口而且可以正常工作。 如果出现错误，错误信息大概会提供为何无法毗连到Kafka的线索。
  

   我在运行上述内容的时候创建失败，原因是我没有事先启动 zookeeper，错误信息如下：

1. [2024-03-29 21:54:03,707] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Node may not be available. (org.apache.kafka.clients.NetworkClient)
2. [2024-03-29 21:54:03,811] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Node may not be available. (org.apache.kafka.clients.NetworkClient)
3. [2024-03-29 21:54:03,913] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Node may not be available. (org.apache.kafka.clients.NetworkClient)
4. [2024-03-29 21:54:04,117] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Node may not be available. (org.apache.kafka.clients.NetworkClient)
5. [2024-03-29 21:54:04,522] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Node may not be available. (org.apache.kafka.clients.NetworkClient)

复制代码

• 然后查察了日志 /opt/homebrew/var/log/kafka/kafka_output.log 内容：
  

1. java.net.ConnectException: Connection refused
2.         at java.base/sun.nio.ch.Net.pollConnect(Native Method)
3.         at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:682)
4.         at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:973)
5.         at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:344)
6.         at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1289)
7. [2024-03-29 21:26:32,648] INFO Opening socket connection to server localhost/[0:0:0:0:0:0:0:1]:2181. (org.apache.zookeeper.ClientCnxn)
8. [2024-03-29 21:26:32,650] WARN Session 0x0 for server localhost/[0:0:0:0:0:0:0:1]:2181, Closing socket connection. Attempting reconnect except it is a SessionExpiredException. (org.apache.zookeeper.ClientCnxn)
9. java.net.ConnectException: Connection refused
10.         at java.base/sun.nio.ch.Net.pollConnect(Native Method)
11.         at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:682)
12.         at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:973)
13.         at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:344)
14.         at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1289)
15. [2024-03-29 21:26:33,220] INFO [ZooKeeperClient Kafka server] Closing. (kafka.zookeeper.ZooKeeperClient)

复制代码

• 可以看到是没有启动 zookeeper，所以手动启动一下：
  

1. brew services start zookeeper

复制代码

• 再重新启动一下 kafka：
  

1. brew services restart kafka

复制代码

• 然后就可以成功运行了，再次测试创建 topic 就成功了
  

server.properties 一览

• 这里展示一下团体的 kafka 的 property 文档，让大家可以看清楚一些：
  

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

复制代码

• 其中最重要的是下面几个（一般必要改动的）：
  
  
  
  • broker.id，如果你设置了一个运算集群，其中有多个 kafka 的节点，那么每个节点都是一个 broker，而每个 broker 的 id 都不能雷同
    
  • #listeners=PLAINTEXT://:9092 这个一般是解释掉的（当默认只有一个节点的时候就默认使用 9092 端口启动这个 broker）但是如果有多个 broker 的时候，请把这里进行修改，使得每个 broker 的监听端口不同，修改的方式就是去掉解释酿成 listeners=PLAINTEXT://:xxxx 其中 xxxx 是你自己想用的端口号
    
  • log.dirs=/opt/homebrew/var/lib/kafka-logs kafka 会默认将日志文件放到这个位置
    
  • zookeeper.connect=localhost:2181 这个是毗连 zookeeper 的端口，也要设置正确
    
  
  
• 另有更多设置的意义，如果大家想深入相识 kafka，发起去 这个网址 去看视频
  

免责声明：如果侵犯了您的权益，请联系站长，我们会及时删除侵权内容，谢谢合作！更多信息从访问主页：qidao123.com:ToB企服之家，中国第一个企服评测及商务社交产业平台。

---

欢迎光临 IT评测·应用市场-qidao123.com (https://dis.qidao123.com/)

Powered by Discuz! X3.4