Skip to content

Commit 2f58869

Browse files
committed
Diff in dist's etc/server.properties
1 parent 21b5db0 commit 2f58869

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

kafka/10broker-config.yml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ data:
7575
7676
############################# Socket Server Settings #############################
7777
78-
# The address the socket server listens on. It will get the value returned from
78+
# The address the socket server listens on. It will get the value returned from
7979
# java.net.InetAddress.getCanonicalHostName() if not configured.
8080
# FORMAT:
8181
# listeners = listener_name://host_name:port
@@ -84,7 +84,7 @@ data:
8484
#listeners=PLAINTEXT://:9092
8585
listeners=OUTSIDE://:9094,PLAINTEXT://:9092
8686
87-
# Hostname and port the broker will advertise to producers and consumers. If not set,
87+
# Hostname and port the broker will advertise to producers and consumers. If not set,
8888
# it uses the value for "listeners" if configured. Otherwise, it will use the value
8989
# returned from java.net.InetAddress.getCanonicalHostName().
9090
#advertised.listeners=PLAINTEXT://your.host.name:9092
@@ -124,7 +124,7 @@ data:
124124
# There are a few important trade-offs here:
125125
# 1. Durability: Unflushed data may be lost if you are not using replication.
126126
# 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.
127-
# 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to exceessive seeks.
127+
# 3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks.
128128
# The settings below allow one to configure the flush policy to flush data after a period of time or
129129
# every N messages (or both). This can be done globally and overridden on a per-topic basis.
130130
@@ -144,8 +144,8 @@ data:
144144
# The minimum age of a log file to be eligible for deletion due to age
145145
log.retention.hours=-1
146146
147-
# A size-based retention policy for logs. Segments are pruned from the log as long as the remaining
148-
# segments don't drop below log.retention.bytes. Functions independently of log.retention.hours.
147+
# A size-based retention policy for logs. Segments are pruned from the log unless the remaining
148+
# segments drop below log.retention.bytes. Functions independently of log.retention.hours.
149149
#log.retention.bytes=1073741824
150150
151151
# The maximum size of a log segment file. When this size is reached a new log segment will be created.

0 commit comments

Comments
 (0)