Kafka日志数据过期了不会自动删除

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 copy the License at
#
#    http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required required applicable law or agreed in writing, software
# distributed under License distributed on
#
# Unless required by applicable law or agreed to in writing, software
# distributed
#
# Unlessnless requiredred byicable lawble law oreed to, software# distributed the ised on"AS IS" BASIS,
# WITHOUT OR OF, either express or.
# See License the language
# limitations under License kafka.KafkaConfig for additional and

############################# Server id the broker must set unique integer for each broker.id BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the BASIS,
# WITHOUT WARRANTIES ORIONS OF ANY KINDe License forpecific languageoverning permissions and
# limitationsations underLicense.

# see kafkaaConfig for additional details and defaults

############################# Server Basics########################

# Thef the brokerer. This must be set to a unique integer for eachWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either BASIS,
# WITHOUT WARRANTIESTIONS OFKINDxpress oried.
# See these forcific language BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either expressSIS,
# WITHOUT WARRANTIES ORR CONDITIONS KIND, either expressimplied.
# 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 ider. Thisbe set toue integerach broker.
broker0

############################# Socket############################ Socketer Settings###################

# The addresslistenswill get fromva.net.InetAddress.getCanonicalHostNamegured.
#   FORMATe://host_name:portXAMPLE:
#     listenersLE:
#     listeners = PLAINTEXThost9092
listeners19092

# Hostname and port the broker will advertise to andconsumers. If note for"listeners" if configured, it will the value from.net.InetAddress().

# Maps listener to security protocols, the default for to be the same. See the config documentation for more details
#listener.security.protocol.map=PLAINTEXT:PLAINTEXT:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL

# The number threads the uses for requests from network and sending responses to the network
num.network.threads=3

# The number of

# The number threads the uses processing, which include disk I/O
num.io.threads

# The number of threads that the server uses for number theer uses forsing requestsquests, whichinclude

# The number of threads that the server uses numberads thater usesocessing requestsinclude

# The number of threads that the server uses numberreads that the serverr processingts, whiche diskum.ios=8

# The send buffer(SO_SNDBUF_SNDBUF) used bye socketr
socket.send.bufferes=102400

# The bufferO_RCVBUF) used therver
socketer.bytes102400

# The maximum size a request the socket will accept (protection against)
socket.max

# The maximum size of a request that the socketat the socket server will accept (protection againstt.request.max.bytes=104857600


############################# Log comma list directories which to log
log.dirs=/home/gateway/environment/kafka_2.12-2.8.0/data

# The number log per. More allow
# parallelism for, but will result more files across
# the brokers.
num.partitions/data

# The default number of log partitions per topic. More partitions/data# The default number partitions per topic. More allow greater
# parallelism for, but thisresult iniles across across
# thers.
num.partitions1

# The of per directory be for recovery startup flushing at shutdown value recommended be increased for installations with dirs in array.
num.recovery.threads.per.data.dir=1

############################# Internal Topic Settings  #############################
# The replication factor for group internal topicsInternal Topic Settings  #############################
# The replication factor for the group

############################# Internal

############################# Internal Topic Settings  #############################
# The replication factor for the

############################# Internal Topicttings  #############################
# The  #############################
# The

############################# Internal Topic Settings  #############################
# The replication factor for

############################# Internal Topic Settings

############################# Internal Topic Settings  #############################
# The replication factor for the group####################### Internal################# Internal##### Internal

############################# Internal Topic Settings  #############################
# The replication factor for the group################### Internal Topic Settings  #############################
# The replication factor for the group metadata

############################# Internal Topic

############################# Internal Topic Settings  #############################
# The replication factor for the

############################# Internalernal Topiche replicationr the group metadata internal topics "__consumer_offsets" and"__transaction_state"
# Forent testingsting, a1 is recommended to ensure availability such as 3.
offsets1
transaction=1
transaction1

############################# Log Flush Policy #############################

# Messages are immediately written the filesystem by we only fsync() to sync
# the OS cache lazily. The following configurations control the flush data disk are few trade here

############################# Log Flush Policy #############################

# Messages are immediately written#################### Logsh Policy #############################

# Messages########################

# Messages are immediately written to the filesystem but by

############################# Log Flushicy #############################

# Messages are immediatelyely written written to theilesystem buttem but by default we only fsync() to sync
# the OS

############################# Log#################### Log############### Log Flush Policy #############################

# Messagesmmediately writtenately writtene filesystemfault we fsyncnc
# the OS cachee lazily. Thelowing configurationsl the flush ofto disk.
# ThereThere aremportant tradetant trades here:
#    1. Durability: Unflushedlushed data may if usingn.
#    2. Latencyarge flushlush intervalsy leadcy spikes whenh does occur asre willf datash.
#    3. Throughput flush generally most operation a small flush may to seeks settings allow to the flush to data a of or N (or). This can done and a-topic.

# The of accept forcing flush data disk.flush.messages Throughput: The flush is generally the most expensive Throughput: The flush is generally the expensiveeration, andll flushterval may may excessive Throughput: The flush is generally the most expensive operation, and a small flush interval seekse settingss below allowconfigureush policy to flushr aa periodf time
# everyry N (or canbegloballyrridden onn ac basis.

# Thecept beforecing a a flush datak
#log.intervalages=10000

# Thesitush.interval1000

############################# Log Retention Policy #############################

# The following configurations control the disposal of log segments. The policy can
# be set to delete segments a period of criteria met. Deletion happens the of.

# The age a file be for due age

# 目前保留72小时，但是去年的数据都还在，没被删除，不清楚为啥没生效
log

############################# Log Retention Policy #############################

# The following configurations control the disposal of log segments. The policy can
# be set to########################## Log##################### Log############### Log Retention Policy #############################

# The##########################

# The###################

# The##############

# The followingations controls control thelog segments. The
# be setsegments afterd of

############################# Log Retention Policy #############################

# The following configurations control

############################# Logion Policy########################

# Thewing configurationsfigurations control

############################# Log Retention Policy #############################

# The following configurations control the disposal of######################## Logion Policy#########################

# Thewing configurations configurations control thesal of log segmentss. The policy can
# be set to deletetion Policy# The following configurations control disposalsegments. The policy bedeleter a periode, or

############################# Log Retention Policy #############################

# The following configurations control the disposal

############################# Log Retention Policy #############################

# Theng configurations controle disposalal of log segments. The policy can
# be set to

############################# Log Retention Policy #############################

# The################

# The

############################# Log Retention Policy #############################

# The following configurations control the disposaltention Policy #############################

# The followinging configurations controlposal oflog segments policyy cann
# beete segmentster ariod ofime, orter aiven sizeccumulated.
# A segment willeted wheneverriteria areetion alwaysappens
# frome endtheTheimum agelog file to be

############################# Log Retention Policy #############################

# The following configurations####################### Log

############################# Log Retention Policy #############################

# The following configurations control the########################## Logetention Policy######################

# The configurations controldisposal ofegments. The

############################# Log Retention PolicyPolicy##################

# Thefigurations controlposal ofgments. Thecy can

############################# Log Retention Policy #############################

# The

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

# 目前保留72小时，但是去年的数据都还在，没被删除，不清楚为啥没生效
log.retention.hours=72

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

############################# 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=localhost:2181

# Timeout in ms for connecting to zookeeper
zookeeper.connection.timeout.ms=18000


############################# 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.
group.initial.rebalance.delay.ms=0

一开始配置的是日志压缩(compact)，后来改为了删除(delete)，但是两者好像都没启到作用，参数配置我服务都会重启下，但是过了2天看了下磁盘还是占用那么多。

随便找了一个Topic的数据文件夹：

• 清理日志：

[2023-03-03 22:57:59,408] INFO Cleaner 0: Beginning cleaning of log __consumer_offsets-7. (kafka.log.LogCleaner)
[2023-03-03 22:57:59,408] INFO Cleaner 0: Building offset map for __consumer_offsets-7... (kafka.log.LogCleaner)
[2023-03-03 22:57:59,438] INFO Cleaner 0: Building offset map for log __consumer_offsets-7 for 1 segments in offset range [423171511, 424550948). (kafka.log.LogCleaner)
[2023-03-03 22:58:00,112] INFO Cleaner 0: Offset map for log __consumer_offsets-7 complete. (kafka.log.LogCleaner)
[2023-03-03 22:58:00,112] INFO Cleaner 0: Cleaning log __consumer_offsets-7 (cleaning prior to Fri Mar 03 22:57:45 CST 2023, discarding tombstones prior to Thu Mar 02 03:12:35 CST 2023)... (kafka.log.LogCleaner)
[2023-03-03 22:58:00,113] INFO Cleaner 0: Cleaning LogSegment(baseOffset=0, size=5775, lastModifiedTime=1677713245727, largestRecordTimestamp=Some(1676529831943)) in log __consumer_offsets-7 into 0 with deletion horizon 1677697955381, retaining deletes. (kafka.log.LogCleaner)
[2023-03-03 22:58:00,113] INFO Cleaner 0: Cleaning LogSegment(baseOffset=421792074, size=7373, lastModifiedTime=1677784355381, largestRecordTimestamp=Some(1677784355381)) in log __consumer_offsets-7 into 0 with deletion horizon 1677697955381, retaining deletes. (kafka.log.LogCleaner)
[2023-03-03 22:58:00,114] INFO Cleaner 0: Swapping in cleaned segment LogSegment(baseOffset=0, size=5775, lastModifiedTime=1677784355381, largestRecordTimestamp=Some(1676529831943)) for segment(s) List(LogSegment(baseOffset=0, size=5775, lastModifiedTime=1677713245727, largestRecordTimestamp=Some(1676529831943)), LogSegment(baseOffset=421792074, size=7373, lastModifiedTime=1677784355381, largestRecordTimestamp=Some(1677784355381))) in log Log(dir=/home/gateway/environment/kafka_2.12-2.8.0/data/__consumer_offsets-7, topic=__consumer_offsets, partition=7, highWatermark=424551142, lastStableOffset=424551142, logStartOffset=0, logEndOffset=424551142) (kafka.log.LogCleaner)
[2023-03-03 22:58:00,115] INFO Cleaner 0: Cleaning LogSegment(baseOffset=423171511, size=104851433, lastModifiedTime=1677855465314, largestRecordTimestamp=Some(1677855465314)) in log __consumer_offsets-7 into 423171511 with deletion horizon 1677697955381, retaining deletes. (kafka.log.LogCleaner)
[2023-03-03 22:58:00,779] INFO Cleaner 0: Swapping in cleaned segment LogSegment(baseOffset=423171511, size=7373, lastModifiedTime=1677855465314, largestRecordTimestamp=Some(1677855465314)) for segment(s) List(LogSegment(baseOffset=423171511, size=104851433, lastModifiedTime=1677855465314, largestRecordTimestamp=Some(1677855465314))) in log Log(dir=/home/gateway/environment/kafka_2.12-2.8.0/data/__consumer_offsets-7, topic=__consumer_offsets, partition=7, highWatermark=424551239, lastStableOffset=424551239, logStartOffset=0, logEndOffset=424551239) (kafka.log.LogCleaner)
[2023-03-03 22:58:00,779] INFO [kafka-log-cleaner-thread-0]: 
    Log cleaner thread 0 cleaned log __consumer_offsets-7 (dirty section = [423171511, 424550948])
    100.0 MB of log processed in 1.4 seconds (72.9 MB/sec).
    Indexed 100.0 MB in 0.7 seconds (142.0 Mb/sec, 51.3% of total time)
    Buffer utilization: 0.0%
    Cleaned 100.0 MB in 0.7 seconds (149.9 Mb/sec, 48.7% of total time)
    Start size: 100.0 MB (1,379,535 messages)
    End size: 0.0 MB (98 messages)
    100.0% size reduction (100.0% fewer messages)
 (kafka.log.LogCleaner)

看不到有错误日志，没有头绪。

生产环境就是每天24小时都会不停的生产数据，Topic相同，都是"gpsdata"，服务器有多个消费者组订阅去后入库。难道一直占用这个Topic，就不会被自动清理数据了吗？