|
| 1 | +# Licensed to the Apache Software Foundation (ASF) under one or more |
| 2 | +# contributor license agreements. See the NOTICE file distributed with |
| 3 | +# this work for additional information regarding copyright ownership. |
| 4 | +# The ASF licenses this file to You under the Apache License, Version 2.0 |
| 5 | +# (the "License"); you may not use this file except in compliance with |
| 6 | +# the License. You may obtain a copy of the License at |
| 7 | +# |
| 8 | +# http://www.apache.org/licenses/LICENSE-2.0 |
| 9 | +# |
| 10 | +# Unless required by applicable law or agreed to in writing, software |
| 11 | +# distributed under the License is distributed on an "AS IS" BASIS, |
| 12 | +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| 13 | +# See the License for the specific language governing permissions and |
| 14 | +# limitations under the License. |
| 15 | + |
| 16 | +################## Why We Need This Separate Config #################### |
| 17 | + |
| 18 | +# While our latest version supports dynamic voters configuration, |
| 19 | +# we will continue using static voter configurations in our Docker Hub images. |
| 20 | +# This decision ensures broader compatibility across different versions and |
| 21 | +# maintains consistent behavior for existing deployments. |
| 22 | +# By retaining static voter implementation in our Docker images, we can provide |
| 23 | +# a more stable and predictable environment for users across various versions of the application. |
| 24 | + |
| 25 | +############################# Server Basics ############################# |
| 26 | + |
| 27 | +# The role of this server. Setting this puts us in KRaft mode |
| 28 | +process.roles=broker,controller |
| 29 | + |
| 30 | +# The node id associated with this instance's roles |
| 31 | +node.id=1 |
| 32 | + |
| 33 | +# The connect string for the controller quorum |
| 34 | +controller.quorum.voters=1@localhost:9093 |
| 35 | + |
| 36 | +############################# Socket Server Settings ############################# |
| 37 | + |
| 38 | +# The address the socket server listens on. |
| 39 | +# Combined nodes (i.e. those with `process.roles=broker,controller`) must list the controller listener here at a minimum. |
| 40 | +# If the broker listener is not defined, the default listener will use a host name that is equal to the value of java.net.InetAddress.getCanonicalHostName(), |
| 41 | +# with PLAINTEXT listener name, and port 9092. |
| 42 | +# FORMAT: |
| 43 | +# listeners = listener_name://host_name:port |
| 44 | +# EXAMPLE: |
| 45 | +# listeners = PLAINTEXT://your.host.name:9092 |
| 46 | +listeners=PLAINTEXT://:9092,CONTROLLER://:9093 |
| 47 | + |
| 48 | +# Name of listener used for communication between brokers. |
| 49 | +inter.broker.listener.name=PLAINTEXT |
| 50 | + |
| 51 | +# Listener name, hostname and port the broker or the controller will advertise to clients. |
| 52 | +# If not set, it uses the value for "listeners". |
| 53 | +advertised.listeners=PLAINTEXT://localhost:9092 |
| 54 | + |
| 55 | +# A comma-separated list of the names of the listeners used by the controller. |
| 56 | +# If no explicit mapping set in `listener.security.protocol.map`, default will be using PLAINTEXT protocol |
| 57 | +# This is required if running in KRaft mode. |
| 58 | +controller.listener.names=CONTROLLER |
| 59 | + |
| 60 | +# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details |
| 61 | +listener.security.protocol.map=CONTROLLER:PLAINTEXT,PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL |
| 62 | + |
| 63 | +# The number of threads that the server uses for receiving requests from the network and sending responses to the network |
| 64 | +num.network.threads=3 |
| 65 | + |
| 66 | +# The number of threads that the server uses for processing requests, which may include disk I/O |
| 67 | +num.io.threads=8 |
| 68 | + |
| 69 | +# The send buffer (SO_SNDBUF) used by the socket server |
| 70 | +socket.send.buffer.bytes=102400 |
| 71 | + |
| 72 | +# The receive buffer (SO_RCVBUF) used by the socket server |
| 73 | +socket.receive.buffer.bytes=102400 |
| 74 | + |
| 75 | +# The maximum size of a request that the socket server will accept (protection against OOM) |
| 76 | +socket.request.max.bytes=104857600 |
| 77 | + |
| 78 | + |
| 79 | +############################# Log Basics ############################# |
| 80 | + |
| 81 | +# A comma separated list of directories under which to store log files |
| 82 | +log.dirs=/tmp/kraft-combined-logs |
| 83 | + |
| 84 | +# The default number of log partitions per topic. More partitions allow greater |
| 85 | +# parallelism for consumption, but this will also result in more files across |
| 86 | +# the brokers. |
| 87 | +num.partitions=1 |
| 88 | + |
| 89 | +# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown. |
| 90 | +# This value is recommended to be increased for installations with data dirs located in RAID array. |
| 91 | +num.recovery.threads.per.data.dir=1 |
| 92 | + |
| 93 | +############################# Internal Topic Settings ############################# |
| 94 | +# The replication factor for the group metadata internal topics "__consumer_offsets", "__share_group_state" and "__transaction_state" |
| 95 | +# For anything other than development testing, a value greater than 1 is recommended to ensure availability such as 3. |
| 96 | +offsets.topic.replication.factor=1 |
| 97 | +share.coordinator.state.topic.replication.factor=1 |
| 98 | +share.coordinator.state.topic.min.isr=1 |
| 99 | +transaction.state.log.replication.factor=1 |
| 100 | +transaction.state.log.min.isr=1 |
| 101 | + |
| 102 | +############################# Log Flush Policy ############################# |
| 103 | + |
| 104 | +# Messages are immediately written to the filesystem but by default we only fsync() to sync |
| 105 | +# the OS cache lazily. The following configurations control the flush of data to disk. |
| 106 | +# There are a few important trade-offs here: |
| 107 | +# 1. Durability: Unflushed data may be lost if you are not using replication. |
| 108 | +# 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. |
| 109 | +# 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks. |
| 110 | +# The settings below allow one to configure the flush policy to flush data after a period of time or |
| 111 | +# every N messages (or both). This can be done globally and overridden on a per-topic basis. |
| 112 | + |
| 113 | +# The number of messages to accept before forcing a flush of data to disk |
| 114 | +#log.flush.interval.messages=10000 |
| 115 | + |
| 116 | +# The maximum amount of time a message can sit in a log before we force a flush |
| 117 | +#log.flush.interval.ms=1000 |
| 118 | + |
| 119 | +############################# Log Retention Policy ############################# |
| 120 | + |
| 121 | +# The following configurations control the disposal of log segments. The policy can |
| 122 | +# be set to delete segments after a period of time, or after a given size has accumulated. |
| 123 | +# A segment will be deleted whenever *either* of these criteria are met. Deletion always happens |
| 124 | +# from the end of the log. |
| 125 | + |
| 126 | +# The minimum age of a log file to be eligible for deletion due to age |
| 127 | +log.retention.hours=168 |
| 128 | + |
| 129 | +# A size-based retention policy for logs. Segments are pruned from the log unless the remaining |
| 130 | +# segments drop below log.retention.bytes. Functions independently of log.retention.hours. |
| 131 | +#log.retention.bytes=1073741824 |
| 132 | + |
| 133 | +# The maximum size of a log segment file. When this size is reached a new log segment will be created. |
| 134 | +log.segment.bytes=1073741824 |
| 135 | + |
| 136 | +# The interval at which log segments are checked to see if they can be deleted according |
| 137 | +# to the retention policies |
| 138 | +log.retention.check.interval.ms=300000 |
0 commit comments