前言

其实每个版本都有些许改动，只不过改动大小而已，但是网上的教程都真的太老了，其实更新一下也费不了多少时间

0.9.0

# 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.

# 节点的ID，必须与其它节点不同

broker.id=0

############################# Socket Server Settings #############################

listeners=PLAINTEXT://:9092

# The port the socket server listens on

# 监听端口

#port=9092

# Hostname the broker will bind to. If not set, the server will bind to all interfaces

# 节点需要绑定的主机名称。如果没有设置，服务器会绑定到所有接口

#host.name=localhost

# Hostname the broker will advertise to producers and consumers. If not set, it uses the

# value for "host.name" if configured.  Otherwise, it will use the value returned from

# java.net.InetAddress.getCanonicalHostName().

# 节点的主机名会通知给生产者和消费者。如果没有设置，它将会使用"host.name"的值（前提是设置了host.name）。

# 否则他会使用java.net.InetAddress.getCanonicalHostName()的返回值

#advertised.host.name=<hostname routable by clients>

# The port to publish to ZooKeeper for clients to use. If this is not set,

# it will publish the same port that the broker binds to.

# 这个端口将暴露给Zookeeper以供客户端来使用。如果没有设置，将会暴露节点绑定的端口

#advertised.port=<port accessible by clients>

# The number of threads handling network requests

# 接受网络请求的线程数

num.network.threads=3

# The number of threads doing disk I/O、

# 进行磁盘IO的线程数

num.io.threads=8

# 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 seperated list of directories under which to store log files

# 一个逗号分隔的目录列表，用来存储日志文件

log.dirs=/tmp/kafka-logs

# 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

# 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

############################# 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.

# 消息直接被写入文件系统，但是默认情况下我们仅仅调用fsync()以延迟的同步系统缓存

# 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 exceessive seeks.

#    1. 持久性:如果不使用复制，未刷新的数据可能会丢失。

#    2. 延迟:非常大的刷新间隔可能会在刷新时导致延迟，因为将会有大量数据刷新。

#    3. 吞吐量:刷新通常是最昂贵的操作，而一个小的刷新间隔可能会导致过多的搜索。

# 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.

# 下面的设置允许你去配置刷新策略，每隔一段时间刷新或者一次N个消息（或者两个都配置）。这可以在全局范围内完成，并在每个主题的基础上重写。

# 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

# 一个日志的最小存活时间，可以被删除

log.retention.hours=168

# A size-based retention policy for logs. Segments are pruned from the log as long as the remaining

# segments don't drop below log.retention.bytes.

# 一个基于大小的日志保留策略。段将被从日志中删除只要剩下的部分段不低于log.retention.bytes。

#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).

# Zookeeper连接字符串（具体见Zookeeper文档）

# This is a comma separated host:port pairs, each corresponding to a zk

# 这是一个以逗号为分割的部分，每一个都匹配一个Zookeeper

# 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.

# 您还可以将一个可选的chroot字符串附加到url，以指定所有kafka znode的根目录。

zookeeper.connect=localhost:2181

# Timeout in ms for connecting to zookeeper

# 连接到Zookeeper的超时时间

zookeeper.connection.timeout.ms=6000

0.10.1

# 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.

# 节点的ID，必须与其它节点不同

broker.id=0

# Switch to enable topic deletion or not, default value is false

# 选择启用删除主题功能，默认false

#delete.topic.enable=true

############################# Socket Server Settings #############################

# The address the socket server listens on. It will get the value returned from

# java.net.InetAddress.getCanonicalHostName() if not configured.

# 套接字服务器坚挺的地址。如果没有配置，就使用java.net.InetAddress.getCanonicalHostName()的返回值

#   FORMAT:格式：

#     listeners = security_protocol://host_name:port

#   EXAMPLE:例子：

#     listeners = PLAINTEXT://your.host.name:9092

#listeners=PLAINTEXT://: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().

# 节点的主机名会通知给生产者和消费者。如果没有设置，如果配置了"listeners"就使用"listeners"的值。

# 否则就使用java.net.InetAddress.getCanonicalHostName()的返回值

#advertised.listeners=PLAINTEXT://your.host.name:9092

# The number of threads handling network requests

# 接受网络请求的线程数

num.network.threads=3

# The number of threads doing disk I/O

# 进行磁盘IO的线程数

num.io.threads=8

# 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 seperated list of directories under which to store log files

# 一个逗号分隔的目录列表，用来存储日志文件

log.dirs=/tmp/kafka-logs

# 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

# 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

############################# 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.

# 消息直接被写入文件系统，但是默认情况下我们仅仅调用fsync()以延迟的同步系统缓存

# 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 exceessive seeks.

#    1. 持久性:如果不使用复制，未刷新的数据可能会丢失。

#    2. 延迟:非常大的刷新间隔可能会在刷新时导致延迟，因为将会有大量数据刷新。

#    3. 吞吐量:刷新通常是最昂贵的操作，而一个小的刷新间隔可能会导致过多的搜索。

# 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.

# 下面的设置允许你去配置刷新策略，每隔一段时间刷新或者一次N个消息（或者两个都配置）。这可以在全局范围内完成，并在每个主题的基础上重写。

# 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

# 一个日志的最小存活时间，可以被删除

log.retention.hours=168

# A size-based retention policy for logs. Segments are pruned from the log as long as the remaining

# segments don't drop below log.retention.bytes.

# 一个基于大小的日志保留策略。段将被从日志中删除只要剩下的部分段不低于log.retention.bytes。

#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).

# Zookeeper连接字符串（具体见Zookeeper文档）

# This is a comma separated host:port pairs, each corresponding to a zk

# 这是一个以逗号为分割的部分，每一个都匹配一个Zookeeper

# 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.

# 您还可以将一个可选的chroot字符串附加到url，以指定所有kafka znode的根目录。

zookeeper.connect=localhost:2181

# Timeout in ms for connecting to zookeeper

# 连接到Zookeeper的超时时间

zookeeper.connection.timeout.ms=6000

0.11.0

# 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.

# 节点的ID，必须与其它节点不同

broker.id=0

# Switch to enable topic deletion or not, default value is false

# 选择启用删除主题功能，默认false

#delete.topic.enable=true

############################# Socket Server Settings #############################

# The address the socket server listens on. It will get the value returned from

# java.net.InetAddress.getCanonicalHostName() if not configured.

# 套接字服务器坚挺的地址。如果没有配置，就使用java.net.InetAddress.getCanonicalHostName()的返回值

#   FORMAT:

#     listeners = listener_name://host_name:port

#   EXAMPLE:

#     listeners = PLAINTEXT://your.host.name:9092

#listeners=PLAINTEXT://: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().

# 节点的主机名会通知给生产者和消费者。如果没有设置，如果配置了"listeners"就使用"listeners"的值。

# 否则就使用java.net.InetAddress.getCanonicalHostName()的返回值

#advertised.listeners=PLAINTEXT://your.host.name: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

# The number of threads that the server uses for processing requests, which may include disk I/O

# 服务器用来处理请求的线程数，可能包括磁盘IO

num.io.threads=8

# 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 seperated list of directories under which to store log files

# 一个逗号分隔的目录列表，用来存储日志文件

log.dirs=/tmp/kafka-logs

# 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

# 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.

# 对于除了开发测试之外的其他任何东西，group元数据内部主题的复制因子“__consumer_offsets”和“__transaction_state”，建议值大于1，以确保可用性(如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.

# 消息直接被写入文件系统，但是默认情况下我们仅仅调用fsync()以延迟的同步系统缓存

# 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 exceessive seeks.

#    1. 持久性:如果不使用复制，未刷新的数据可能会丢失。

#    2. 延迟:非常大的刷新间隔可能会在刷新时导致延迟，因为将会有大量数据刷新。

#    3. 吞吐量:刷新通常是最昂贵的操作，而一个小的刷新间隔可能会导致过多的搜索。

# 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.

# 下面的设置允许你去配置刷新策略，每隔一段时间刷新或者一次N个消息（或者两个都配置）。这可以在全局范围内完成，并在每个主题的基础上重写。

# 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

# 一个日志的最小存活时间，可以被删除

log.retention.hours=168

# A size-based retention policy for logs. Segments are pruned from the log as long as the remaining

# segments don't drop below log.retention.bytes.

# 一个基于大小的日志保留策略。段将被从日志中删除只要剩下的部分段不低于log.retention.bytes。

#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).

# Zookeeper连接字符串（具体见Zookeeper文档）

# This is a comma separated host:port pairs, each corresponding to a zk

# 这是一个以逗号为分割的部分，每一个都匹配一个Zookeeper

# 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.

# 您还可以将一个可选的chroot字符串附加到url，以指定所有kafka znode的根目录。

zookeeper.connect=localhost:2181

# Timeout in ms for connecting to zookeeper

# 连接到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

小结

可以看出，目前最新版本的配置文件没有了

#port=9092

#host.name=localhost

#advertised.host.name=<hostname routable by clients>

#advertised.port=<port accessible by clients>

取而代之的是

#listeners=PLAINTEXT://:9092

#advertised.listeners=PLAINTEXT://your.host.name:9092

并且新增了一些配置，以及有些地方注释的说明更详细。

=====================2020.4.15更新=====================

1.1.1、2.0.0、2.1.1、2.2.0、2.3.0、2.4.1

# 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.

# 节点的ID，必须与其它节点不同

broker.id=0

############################# 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

# 套接字服务器监听的地址。如果没有配置，就使用java.net.InetAddress.getCanonicalHostName()的返回值

#listeners=PLAINTEXT://: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

# 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

# The number of threads that the server uses for processing requests, which may include disk I/O

# 进行磁盘IO的线程数

num.io.threads=8

# 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

# 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

# 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"

# 内部主题“_consumer_offsets”和“_transaction_state”的复制因子

# For anything other than development testing, a value greater than 1 is recommended for to ensure availability such as 3.

# 对于开发测试以外的任何情况，建议使用大于1的值来确保可用性，比如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.

# 消息直接被写入文件系统，但是默认情况下我们仅仅调用fsync()以延迟的同步系统缓存

# 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.

#    1. 持久性:如果不使用复制，未刷新的数据可能会丢失。

#    2. 延迟:非常大的刷新间隔可能会在刷新时导致延迟，因为将会有大量数据刷新。

#    3. 吞吐量:刷新通常是最昂贵的操作，而一个小的刷新间隔可能会导致过多的搜索。

# 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.

# 下面的设置允许你去配置刷新策略，每隔一段时间刷新或者一次N个消息（或者两个都配置）。这可以在全局范围内完成，并在每个主题的基础上重写。

# 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

# 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，段将从日志中删除。

#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地址，多个以逗号分隔，还可以在最后指定kafka存储的namespace：eg："127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002/kafka"

zookeeper.connect=localhost:2181

# Timeout in ms for connecting to zookeeper

# 连接到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.

# 指定GroupCoordinator延迟初始消费者再平衡的时间(以毫秒为单位)

# 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.

# 默认值是3秒

# 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.

# 在生产环境中，3秒的默认值更合适

group.initial.rebalance.delay.ms=0

更多详细配置见官网：http://kafka.apache.org/documentation/#configuration

生产端配置

# 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 org.apache.kafka.clients.producer.ProducerConfig for more details

############################# Producer Basics #############################

# list of brokers used for bootstrapping knowledge about the rest of the cluster

# format: host1:port1,host2:port2 ...

bootstrap.servers=localhost:9092

# 指定数据压缩格式：none、gzip、snappy、lz4、zstd

compression.type=none

# name of the partitioner class for partitioning events; default partition spreads data randomly

# 分区策略，默认随机

#partitioner.class=

# the maximum amount of time the client will wait for the response of a request

# 客户端等待请求响应的最大时间，即在向 producer 发送 ack 之前，broker允许等待的最大时间

#request.timeout.ms=

# how long `KafkaProducer.send` and `KafkaProducer.partitionsFor` will block for

# `KafkaProducer.send` and `KafkaProducer.partitionsFor`阻塞的时间

#max.block.ms=

# the producer will wait for up to the given delay to allow other records to be sent so that the sends can be batched together

# 生产者将等待一个延迟，以便和其他的消息组合成一个批次发出，减少发送的请求数

#linger.ms=

# the maximum size of a request in bytes

# 请求的最大字节数

#max.request.size=

# the default batch size in bytes when batching multiple records sent to a partition

# 在批处理消息发送到一个分区的多个记录时的批处理大小，默认16k

#batch.size=

# the total bytes of memory the producer can use to buffer records waiting to be sent to the server

# 生产者可以用来缓存消息的缓冲区大小

#buffer.memory=

# 以下是默认配置文件没有的：更多 http://kafka.apache.org/documentation/#producerconfigs

# 在请求完成之前，生产者要求leader已收到确认消息的数量。

# 0：生产者不会等待服务器的ack响应，不保证服务器收到消息，返回的偏移量总是-1

# 1：leader将消息写入本地日志，但不会管其他follower是否写入。

# all：leader和所有的follower都成功同步消息才会返回ack，保证消息不会丢失。all等价于-1.

acks=

Kafka配置文件server.properties（三个版本）的更多相关文章

  1. kafka的server.properties配置文件参考示范（图文详解）（多种方式）

    简单点的,就是 kafka_2.11-0.8.2.2.tgz的3节点集群的下载.安装和配置(图文详解) 但是呢,大家在实际工作中,会一定要去牵扯到调参数和调优问题的.以下,是我给大家分享的kafka的 ...

  2. 、第1节 kafka消息队列：8、9、kafka的配置文件server.properties的说明

    10.kafka的配置文件说明 Server.properties配置文件说明 #broker的全局唯一编号,不能重复 broker.id=0 #用来监听链接的端口,producer或consumer ...

  3. kafka 的server.properties

    # Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreement ...

  4. kafka中server.properties配置文件参数说明

    转自:http://blog.csdn.net/lizhitao/article/details/25667831 参数 说明(解释) broker.id =0 每一个broker在集群中的唯一表示, ...

  5. apache kafka系列之server.properties配置文件参数说明

    每个kafka broker中配置文件server.properties默认必须配置的属性如下: broker.id=0num.network.threads=2num.io.threads=8soc ...

  6. Kafka源码分析(三) - Server端 - 消息存储

    系列文章目录 https://zhuanlan.zhihu.com/p/367683572 目录 系列文章目录 一. 业务模型 1.1 概念梳理 1.2 文件分析 1.2.1 数据目录 1.2.2 . ...

  7. 【server.properties】kafka服务设置

    每个kafka broker中配置文件server.properties默认必须配置的属性如下: broker.id=0 num.network.threads=2 num.io.threads=8 ...

  8. Hadoop生态圈-Kafka配置文件详解

    Hadoop生态圈-Kafka配置文件详解 作者:尹正杰 版权声明:原创作品,谢绝转载!否则将追究法律责任. 一.默认kafka配置文件内容([yinzhengjie@s101 ~]$ more /s ...

  9. 在kafka/config/目录下面有3个配置文件参数说明（producer.properties。consumer.properties。server.properties）

    (1).producer.properties:生产端的配置文件 #指定kafka节点列表,用于获取metadata,不必全部指定 #需要kafka的服务器地址,来获取每一个topic的分片数等元数据 ...

随机推荐

  1. LVS负载均衡-基础知识梳理

    一. 集群的概念 服务器集群简称集群是一种服务器系统,它通过一组松散集成的服务器软件和/或硬件连接起来高度紧密地协作完成计算工作.在某种意义上,他们可以被看作是一台服务器.集群系统中的单个服务器通常称 ...

  2. Daily Scrumming* 2015.12.19（Day 11）

    一.团队scrum meeting照片 二.成员工作总结 姓名 任务ID 迁入记录 江昊 任务1090 https://github.com/buaaclubs-team/temp-front/com ...

  3. 【MOOC EXP】Linux内核分析实验八报告

    程涵  原创博客 <Linux内核分析>MOOC课程http://mooc.study.163.com/course/USTC-1000029000 进程的切换和系统的一般执行过程 知识点 ...

  4. Linux内核分析——字符集总结与分析

      一.  设置修改系统.应用默认字符集 1. 查看虚拟机的字符集: 由此可见,该虚拟机的字符集为zh_CN.UTF-8. 2. 查看服务器支持的编码方式 3. 修改字符集类型 上图可见,LANG字符 ...

  5. 20135323符运锦----第七周：Linux内核如何装载和启动一个可执行程序

    可执行程序的装载 一.预处理.编译.链接和目标文件的格式 1.可执行程序是怎么得来的 ①编译器预处理 gcc -E -o XX.cpp XX.c (-m32)// 注:把include的文件包含进来, ...

  6. QQ互联登录提示redirect uri is illegal(100010)完美解决方法

    大概2015年3月低,腾讯QQ互联开发平台调整了有关QQ登录应用回调地址填写规则,用来修复QQ登录过程因回调地址的漏洞可能导致存在的安全问题. 博主接触这块较多,但也是四月才了解此事,从4月起,所有新 ...

  7. JIRA & GitHub

    JIRA & GitHub https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-81418 ...

  8. java解析Json字符串之懒人大法

    面对Java解析Json字符串的需求,有很多开源工具供我们选择,如google的Gson.阿里巴巴的fastJson.在网上能找到大量的文章讲解这些工具的使用方法.我也是参考这些文章封装了自己的Jso ...

  9. Ubuntu 16.04 root环境变量不生效问题解决方案

    在Ubuntu 16.04中配置JDK环境变量,但是在切换到root时不生效 . 在/etc/profile中添加如下: export JAVA_HOME=/opt/java/jdk1..0_151 ...

  10. selenium之截图

    selenium支持对当前页面保存截图,使用方法: driver.get_screenshot_as_file(file_path) 代码举例: ...... def get_screenshot(d ...