zookeeper.connect

该参数用于配置Kafka要连接的Zookeeper/集群的地址。
它的值是一个字符串，使用逗号分隔Zookeeper的多个地址。Zookeeper的单个地址是 host:port
形式的，可以在最后添加Kafka在Zookeeper中的根节点路径。 

  1. zookeeper.connect=localhost:2181/myKafka

listeners

用于指定当前Broke向外发布服务的地址和端口
可与adadvertised.listeners 配合，用于做内外网隔离。 

  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. # see kafka.server.KafkaConfig for additional details and defaults
  18. ############################# Server Basics #############################
  20. # The id of the broker. This must be set to a unique integer for each broker.
  21. broker.id=0
  23. ############################# Socket Server Settings #############################
  25. # The address the socket server listens on. It will get the value returned from 
  26. # java.net.InetAddress.getCanonicalHostName() if not configured.
  27. #   FORMAT:
  28. #     listeners = listener_name://host_name:port
  29. #   EXAMPLE:
  30. #i     listeners = PLAINTEXT://your.host.name:9092
  31. listeners=PLAINTEXT://172.28.247.169:9092  
  32. advertised.listeners=PLAINTEXT://8.130.163.189: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 seperated list of directories under which to store log files
  61. log.dirs=/tmp/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=1
  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 for to ensure availability such as 3.
  75. offsets.topic.replication.factor=1
  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 exceessive 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=localhost:2181/myKafka
  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