Kakfa Server配置文件的介紹

# The id of the broker. This must be set to a unique integer for each broker.

# 節(jié)點(diǎn)的ID，必須與其它節(jié)點(diǎn)不同

broker.id=0

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

# 選擇啟用刪除主題功能，默認(rèn)false

delete.topic.enable=true

unclean.leader.election.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.

#   FORMAT:

#     listeners = listener_name://host_name:port

#   EXAMPLE:

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

# 監(jiān)聽端口及IP

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

# 接受網(wǎng)絡(luò)請求的線程數(shù)

num.network.threads=6

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

# 進(jìn)行磁盤IO的線程數(shù)

num.io.threads=16

# The send buffer (SO_SNDBUF) used by the socket server

# 套接字服務(wù)器使用的發(fā)送緩沖區(qū)大小

socket.send.buffer.bytes=102400

# The receive buffer (SO_RCVBUF) used by the socket server

# 套接字服務(wù)器使用的接收緩沖區(qū)大小

socket.receive.buffer.bytes=102400

# The maximum size of a request that the socket server will accept (protection against OOM)

# 單個(gè)請求最大能接收的數(shù)據(jù)量

socket.request.max.bytes=104857600

############################# Log Basics #############################

# A comma seperated list of directories under which to store log files

# 一個(gè)逗號分隔的目錄列表，用來存儲日志文件

log.dirs=/data/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.

# 每個(gè)主題的日志分區(qū)的默認(rèn)數(shù)量。更多的分區(qū)允許更大的并行操作，但是它會導(dǎo)致節(jié)點(diǎn)產(chǎn)生更多的文件

num.partitions=6

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

# 每個(gè)數(shù)據(jù)目錄中的線程數(shù)，用于在啟動時(shí)日志恢復(fù)，并在關(guān)閉時(shí)刷新。

num.recovery.threads.per.data.dir=4

## 是否開啟日志壓縮

log.cleaner.enable=true

## 是否允許控制器關(guān)閉broker ,若是設(shè)置為true,會關(guān)閉所有在這個(gè)broker上的leader，并轉(zhuǎn)移到其他broker

controlled.shutdown.enable=true

#如果unclean.leader.election.enable參數(shù)的值為false，那么就意味著非ISR中的副本不能夠參與選舉，此時(shí)無法進(jìn)行新的選舉，此時(shí)整個(gè)分區(qū)處于不可用狀態(tài)。如果unclean.leader.election.enable參數(shù)的值為true，那么可以從非ISR集合中選舉follower副本稱為新的leader。

unclean.leader.election.enable=false

## 一個(gè)topic ，默認(rèn)分區(qū)的replication個(gè)數(shù) ，不得大于集群中broker的個(gè)數(shù)

default.replication.factor=3

## 是否允許自動創(chuàng)建topic ，若是false，就需要通過命令創(chuàng)建topic

auto.create.topics.enable=false

## leader 進(jìn)行復(fù)制的線程數(shù)，增大這個(gè)數(shù)值會增加follower的IO

num.replica.fetchers=2

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

# 內(nèi)部主題設(shè)置

# 對于除了開發(fā)測試之外的其他任何東西，group元數(shù)據(jù)內(nèi)部主題的復(fù)制因子“__consumer_offsets”和“__transaction_state”，建議值大于1，以確保可用性(如3)。

offsets.topic.replication.factor=3

transaction.state.log.replication.factor=3

transaction.state.log.min.isr=2

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

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

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

# 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

# 一個(gè)日志的最小存活時(shí)間，可以被刪除

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. Functions independently of log.retention.hours.

#log.retention.bytes=1073741824

# The maximum size of a log segment file. When this size is reached a new log segment will be created.

# 每一個(gè)日志段大小的最大值。當(dāng)?shù)竭_(dá)這個(gè)大小時(shí)，會生成一個(gè)新的片段。

log.segment.bytes=1073741824

# The interval at which log segments are checked to see if they can be deleted according

# to the retention policies

# 檢查日志段的時(shí)間間隔，看是否可以根據(jù)保留策略刪除它們

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連接字符串

# 這是一個(gè)以逗號為分割的部分，每一個(gè)都匹配一個(gè)Zookeeper

# 您還可以將一個(gè)可選的chroot字符串附加到url，以指定所有kafka znode的根目錄。

zookeeper.connect=192.168.1.235:2181,192.168.1.236:2181,192.168.1.237:2181

# Timeout in ms for connecting to zookeeper

# 連接到Zookeeper的超時(shí)時(shí)間

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.

#讓coordinator推遲空消費(fèi)組接收到成員加入請求后本應(yīng)立即開啟的rebalance

group.initial.rebalance.delay.ms=3000