Article From:https://www.cnblogs.com/yinzhengjie/p/9216974.html

                    HadoopDetailed interpretation of the -Kafka configuration file of the ecosystem

                                      Author: Yin Zhengjie

Copyright declaration: original works, refuse to reprint! Otherwise, the legal responsibility will be investigated.

 

 

 

 

I. default Kafka configuration file content ([yinzhengjie@s101 to] $more /soft/kafka/config/server.properties)

[yinzhengjie@s101 ~]$ more /soft/kafka/config/server.properties 
# 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.
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
listeners=PLAINTEXT://s101: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
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=/home/yinzhengjie/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.
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.
# 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.
# 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
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=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.connect=s102:2181,s103:2181,s104:2181

# Timeout in ms 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 st
artup.
group.initial.rebalance.delay.ms=0
[yinzhengjie@s101 ~]$ 

 

Two.Kafka commonly used parameters

1>.broker.id

  Answer: the only identity identity of the Kafka node service (similar to the myid of the zookeeper), if the broker.id of multiple Kafka nodes is repeated, only one node can provide the service normally.

2>.listeners=PLAINTEXT://s101:9092

  Answer:listeners For the listener port, PLAINTEXT represents plain text (that is, no matter what type of data you send, YISHION text is received, including pictures, video and so on, but it may be a messy code if you receive it and open it again!). S101:9092 represents the host name and port number.

3>.num.network.threads=3

  Answer: the default number of network threads is 3.

4>.num.io.threads=8

  Answer: the default I/O thread is 8.

5>.socket.send.buffer.bytes=102400

  Answer: the default socket send buffer is 100K

6>.socket.receive.buffer.bytes=102400

  Answer: the default tao-jiezi acceptance buffer is 100k.

7>.socket.request.max.bytes=104857600

  Answer: the maximum number of bytes received by default is 100M.

8>.log.dirs=/home/yinzhengjie/kafka/logs

  Answer: specify the real data for storing Kafka. I have real data here./home/yinzhengjie/kafka/logs”。

9>.num.partitions=1

  Answer: the default number of partitions is 1.

10>.num.recovery.threads.per.data.dir=1

  Answer: the default recovery thread for each folder is 1.

11>.log.retention.hours=168

  Answer: the default data retention time is 168 hours, that is, a week.(7Day.

12>.log.segment.bytes=1073741824

   Answer: specify that the maximum data for each data log is 1G. When this value is exceeded, the log will scroll automatically.

13>.log.retention.check.interval.ms=300000

   Answer: check whether the log is expired every 300 seconds (5 minutes), and if the data exceeds the inventory date (the default 7 days), the corresponding data in the log will be deleted.

14>.zookeeper.connect=s102:2181,s103:2181,s104:2181

   Answer: specify zookeeper server, if there are multiple, need to be separated by commas.

15>.zookeeper.connection.timeout.ms=6000

  Answer: set the zookeeper connection timeout time (the default is 6 seconds). If the connection is still not connected to this specified time, the node has been hung up by default.

16>.

 

 

 

Three.

 

Leave a Reply

Your email address will not be published. Required fields are marked *