0


docker启动kafka并挂载配置文件,并让外部环境连接kafka

docker 启动 kafka 并挂载配置文件,并让外部环境连接 kafka

拉取 kafka 镜像

  1. docker pull apache/kafka:3.7.0

通过 docker 启动 kafka

  1. docker run -d--name kafka -p9092:9092 apache/kafka:3.7.0

创建宿主机的目录

创建宿主机的目录的作用是存放配置文件

  1. mkdir-p /docker-data/kafka-data/

将 docker 容器中的文件复制到宿主机

  1. dockercp kafka:/etc/kafka/docker/server.properties /docker-data/kafka-data/

关闭容器

  1. dockerrm-f kafka

修改配置文件

  1. vim /docker-data/kafka-data/server.properties

内容如下(只需要修改 43 行和 51 行的 IP 就可以)

  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.
  15. #
  16. # This configuration file is intended for use in KRaft mode, where
  17. # Apache ZooKeeper is not present.
  18. #
  19. ############################# Server Basics #############################
  20. # The role of this server. Setting this puts us in KRaft mode
  21. process.roles=broker,controller
  22. # The node id associated with this instance's roles
  23. node.id=1
  24. # The connect string for the controller quorum
  25. controller.quorum.voters=1@localhost:9093
  26. ############################# Socket Server Settings #############################
  27. # The address the socket server listens on.
  28. # Combined nodes (i.e. those with `process.roles=broker,controller`) must list the controller listener here at a minimum.
  29. # If the broker listener is not defined, the default listener will use a host name that is equal to the value of java.net.InetAddress.getCanonicalHostName(),
  30. # with PLAINTEXT listener name, and port 9092.
  31. # FORMAT:
  32. # listeners = listener_name://host_name:port
  33. # EXAMPLE:
  34. # listeners = PLAINTEXT://your.host.name:9092
  35. # 把 IP 配置成 0.0.0.0
  36. listeners=PLAINTEXT://0.0.0.0:9092,CONTROLLER://0.0.0.0:9093
  37. # Name of listener used for communication between brokers.
  38. inter.broker.listener.name=PLAINTEXT
  39. # Listener name, hostname and port the broker will advertise to clients.
  40. # If not set, it uses the value for "listeners".
  41. # 我们要通过 linux 访问 docker 容器中的 kafka 所以把 IP 配置成 linux 的 IP
  42. advertised.listeners=PLAINTEXT://自己的 IP:9092
  43. # A comma-separated list of the names of the listeners used by the controller.
  44. # If no explicit mapping set in `listener.security.protocol.map`, default will be using PLAINTEXT protocol
  45. # This is required if running in KRaft mode.
  46. controller.listener.names=CONTROLLER
  47. # Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
  48. listener.security.protocol.map=CONTROLLER:PLAINTEXT,PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL
  49. # The number of threads that the server uses for receiving requests from the network and sending responses to the network
  50. num.network.threads=3
  51. # The number of threads that the server uses for processing requests, which may include disk I/O
  52. num.io.threads=8
  53. # The send buffer (SO_SNDBUF) used by the socket server
  54. socket.send.buffer.bytes=102400
  55. # The receive buffer (SO_RCVBUF) used by the socket server
  56. socket.receive.buffer.bytes=102400
  57. # The maximum size of a request that the socket server will accept (protection against OOM)
  58. socket.request.max.bytes=104857600
  59. ############################# Log Basics #############################
  60. # A comma separated list of directories under which to store log files
  61. log.dirs=/tmp/kraft-combined-logs
  62. # The default number of log partitions per topic. More partitions allow greater
  63. # parallelism for consumption, but this will also result in more files across
  64. # the brokers.
  65. num.partitions=1
  66. # The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
  67. # This value is recommended to be increased for installations with data dirs located in RAID array.
  68. num.recovery.threads.per.data.dir=1
  69. ############################# Internal Topic Settings #############################
  70. # The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
  71. # For anything other than development testing, a value greater than 1 is recommended to ensure availability such as 3.
  72. offsets.topic.replication.factor=1
  73. transaction.state.log.replication.factor=1
  74. transaction.state.log.min.isr=1
  75. ############################# Log Flush Policy #############################
  76. # Messages are immediately written to the filesystem but by default we only fsync() to sync
  77. # the OS cache lazily. The following configurations control the flush of data to disk.
  78. # There are a few important trade-offs here:
  79. # 1. Durability: Unflushed data may be lost if you are not using replication.
  80. # 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.
  81. # 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks.
  82. # The settings below allow one to configure the flush policy to flush data after a period of time or
  83. # every N messages (or both). This can be done globally and overridden on a per-topic basis.
  84. # The number of messages to accept before forcing a flush of data to disk
  85. #log.flush.interval.messages=10000
  86. # The maximum amount of time a message can sit in a log before we force a flush
  87. #log.flush.interval.ms=1000
  88. ############################# Log Retention Policy #############################
  89. # The following configurations control the disposal of log segments. The policy can
  90. # be set to delete segments after a period of time, or after a given size has accumulated.
  91. # A segment will be deleted whenever *either* of these criteria are met. Deletion always happens
  92. # from the end of the log.
  93. # The minimum age of a log file to be eligible for deletion due to age
  94. log.retention.hours=168
  95. # A size-based retention policy for logs. Segments are pruned from the log unless the remaining
  96. # segments drop below log.retention.bytes. Functions independently of log.retention.hours.
  97. #log.retention.bytes=1073741824
  98. # The maximum size of a log segment file. When this size is reached a new log segment will be created.
  99. log.segment.bytes=1073741824
  100. # The interval at which log segments are checked to see if they can be deleted according
  101. # to the retention policies
  102. log.retention.check.interval.ms=300000

通过 docker 启动 kafka 并挂载配置文件

  1. docker run -d--name kafka --restart=always -p9092:9092 -v /docker-data/kafka-data:/mnt/shared/config apache/kafka:3.7.0

这样就通过 docker 启动 kafka 了,然后就可以通过外部环境连接了,如果还是连接不了,那就检查一下是否对外开放 9092、9093 这两个端口

标签: docker kafka 容器

本文转载自: https://blog.csdn.net/q2570558854/article/details/141687742
版权归原作者 晚枫2000 所有, 如有侵权,请联系我们删除。

“docker启动kafka并挂载配置文件,并让外部环境连接kafka”的评论:

还没有评论