Shulou(Shulou.com)05/31 Report--

This article is about what the kafka parameter configuration broker means. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

# the ID uniquely identified in the cluster is required to be a positive number.

Broker.id=0

# Service port. Default is 9092.

Port=9092

# listening address, not set to all addresses

Host.name=debugo01

# maximum number of threads to process network requests

Num.network.threads=2

# number of threads processing disk IBO

Num.io.threads=8

# number of backstage threads

Background.threads = 4

# maximum number of request queues waiting to be processed by IO threads

Queued.max.requests = 500,

# send buffer (SO_SNDBUF) of socket

Socket.send.buffer.bytes=1048576

# receive buffer (SO_RCVBUF) of socket

Socket.receive.buffer.bytes=1048576

# maximum number of bytes requested by socket. To prevent memory overflow, the message.max.bytes must be less than

Socket.request.max.bytes = 104857600

# # Topic # #

# the number of partitions per topic, more partition will result in more segment file

Num.partitions=2

# whether to allow automatic creation of topic? for false, you need to create topic by command

Auto.create.topics.enable = true

# A topic. The number of replication in the default partition cannot be greater than the number of broker in the cluster.

Default.replication.factor = 1

# the maximum size of the message body in bytes

Message.max.bytes = 1000000

# # ZooKeeper # #

# Zookeeper quorum settings. If more than one is separated by a comma

Zookeeper.connect=debugo01:2181,debugo02,debugo03

# timeout for connecting to zk

Zookeeper.connection.timeout.ms=1000000

# actual synchronization between leader and follower in a ZooKeeper cluster

Zookeeper.sync.time.ms = 2000

# # Log # #

# logs are stored in directories. Multiple directories are separated by commas

Log.dirs=/var/log/kafka

# when the number of messages below is reached, the data will be flush to the log file. Default 10000

# log.flush.interval.messages=10000

# perform a forced flush operation when the following time (ms) is reached. No matter which interval.ms or interval.messages achieves, it will flush. Default 3000ms

# log.flush.interval.ms=1000

# check whether the interval between log flush

Log.flush.scheduler.interval.ms = 3000

# Log cleanup policy (delete | compact)

Log.cleanup.policy = delete

# Log retention time (hours | minutes). Default is 7 days (168h). After this time, the data will be processed according to the policy. Either bytes or minutes will be triggered no matter which one is reached first.

Log.retention.hours=168

# the maximum number of bytes stored in log data. After this time, the data will be processed according to the policy.

# log.retention.bytes=1073741824

# Control the size of the log segment file. If you exceed this size, append it to a new log segment file (- 1 means there is no limit)

Log.segment.bytes=536870912

# A new segment will be forced when the following time is reached

Log.roll.hours = 2407

# check cycle of log fragment files to see if they meet the deletion policy settings (log.retention.hours or log.retention.bytes)

Log.retention.check.interval.ms=60000

# whether to enable compression

Log.cleaner.enable=false

# maximum retention time for compressed logs

Log.cleaner.delete.retention.ms = 1 day

# Index file size limit for segment logs

Log.index.size.max.bytes = 10 * 1024 * 1024

# y A buffer for index calculation, which generally does not need to be set.

Log.index.interval.bytes = 4096

# # replica # #

# timeout of communication between partition management controller and replicas

Controller.socket.timeout.ms = 30000

# size of controller-to-broker-channels message queue

Controller.message.queue.size=10

# the maximum waiting time for replicas to respond to leader. If this time is exceeded, replicas is excluded from management.

Replica.lag.time.max.ms = 10000

# whether the controller is allowed to disable broker. If set to true, all leader on this broker will be closed and transferred to other broker.

Controlled.shutdown.enable = false

# number of attempts to shut down the controller

Controlled.shutdown.max.retries = 3

# interval between each shutdown attempt

Controlled.shutdown.retry.backoff.ms = 5000

# if the relicas lags too far behind, the partition relicas will be considered invalid. In general, the synchronization of messages in replicas always lags behind because of network delay and other reasons. If the message is seriously lagging, leader will consider the relicas network to have a large latency or limited message throughput. In environments where the number of broker is small, or the network is insufficient, it is recommended to increase this value.

Replica.lag.max.messages = 4000

# socket timeout for leader and relicas

Replica.socket.timeout.ms= 30 * 1000

# socket cache size of leader replication

Replica.socket.receive.buffer.bytes=64 * 1024

# maximum number of bytes that replicas acquires data at a time

Replica.fetch.max.bytes = 1024 * 1024

# maximum waiting time for communication between replicas and leader. If it fails, it will try again.

Replica.fetch.wait.max.ms = 500,

# the minimum data size for each fetch operation. If the data in leader that has not been synchronized is insufficient, it will wait until the data reaches this size.

Replica.fetch.min.bytes = 1

# the number of threads replicated in leader. Increasing this number increases the IO of relipca.

Num.replica.fetchers = 1

# interval between flush of the highest water level for each replica

Replica.high.watermark.checkpoint.interval.ms = 5000

# whether to automatically balance the allocation policy between broker

Auto.leader.rebalance.enable = false

# the imbalance ratio of leader. If it exceeds this value, the partition will be rebalanced.

Leader.imbalance.per.broker.percentage = 10

# time interval to check whether leader is unbalanced

Leader.imbalance.check.interval.seconds = 300

# maximum amount of space that the client retains offset information

Offset.metadata.max.bytes = 1024

Thank you for reading! This is the end of this article on "what is the meaning of kafka parameter configuration broker?". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it out for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.