Shulou(Shulou.com)06/03 Report--

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

# Node's ID, which must be different from other nodes

Broker.id=0

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

# Select to enable the delete theme feature. Default is 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

# listening port and 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

# number of threads accepting network requests

Num.network.threads=6

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

# number of threads performing disk IO

Num.io.threads=16

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

# send buffer size used by the socket server

Socket.send.buffer.bytes=102400

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

# receive buffer size 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)

# maximum amount of data that can be received by a single request

Socket.request.max.bytes=104857600

# # Log Basics # #

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

# A comma-separated list of directories to store log files

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.

# the default number of log partitions per topic. More partitions allow larger parallel operations, but it causes nodes to produce more files

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.

# the number of threads in each data directory for log recovery at startup and refresh at shutdown.

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

# # whether to enable log compression

Log.cleaner.enable=true

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

# if the value of the unclean.leader.election.enable parameter is false, it means that the copy in the non-ISR cannot participate in the election, the new election cannot be held at this time, and the entire partition is unavailable. If the value of the unclean.leader.election.enable parameter is true, you can elect a copy of follower from a non-ISR collection to be called the new leader.

Unclean.leader.election.enable=false

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

Default.replication.factor=3

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

Auto.create.topics.enable=false

# # the number of threads copied by leader. Increasing this value will increase the IO of follower

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.

# Internal theme settings

For anything other than development testing, the replication factors "_ _ consumer_offsets" and "_ _ transaction_state" of the theme inside the group metadata are recommended to be greater than 1 to ensure availability (for example, 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

# the minimum survival time of a log, which can be deleted

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.

# the maximum size of each log segment. When this size is reached, a new fragment is generated.

Log.segment.bytes=1073741824

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

# to the retention policies

# check the interval of log segments to see if they can be deleted according to the retention policy

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.1virtual 3000127.0.0.1" 1127.0.0.1 ".

# You can also append an optional chroot string to the urls to specify the

# root directory for all kafka znodes.

# Zookeeper connection string

# this is a section separated by commas, each matching a Zookeeper

# you can also append an optional chroot string to url to specify the root directories of all kafka znode.

Zookeeper.connect=192.168.1.235:2181192.168.1.236:2181192.168.1.237:2181

# Timeout in ms for connecting to zookeeper

# timeout for connecting to 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.

# Let coordinator postpone the rebalance that should have been opened immediately after the empty consumer group received the member's request to join

Group.initial.rebalance.delay.ms=3000

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.