You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Luke Chen (Jira)" <ji...@apache.org> on 2024/03/19 08:21:00 UTC
[jira] [Created] (KAFKA-16385) Segment is rolled before segment.ms or segment.bytes breached
Luke Chen created KAFKA-16385:
---------------------------------
Summary: Segment is rolled before segment.ms or segment.bytes breached
Key: KAFKA-16385
URL: https://issues.apache.org/jira/browse/KAFKA-16385
Project: Kafka
Issue Type: Bug
Affects Versions: 3.7.0
Reporter: Luke Chen
Steps to reproduce:
1. Creating a topic with the config: segment.ms=7days , retention.ms=1sec .
2. Send a record "aaa" to the topic
3. Wait for 1 second
Will this segment will rolled? I thought no.
But what I have tested is it will roll:
{code:java}
[2024-03-19 15:23:13,924] INFO [LocalLog partition=t2-1, dir=/tmp/kafka-logs_jbod] Rolled new log segment at offset 1 in 3 ms. (kafka.log.LocalLog)
[2024-03-19 15:23:13,925] INFO [ProducerStateManager partition=t2-1] Wrote producer snapshot at offset 1 with 1 producer ids in 1 ms. (org.apache.kafka.storage.internals.log.ProducerStateManager)
[2024-03-19 15:23:13,925] INFO [UnifiedLog partition=t2-1, dir=/tmp/kafka-logs_jbod] Deleting segment LogSegment(baseOffset=0, size=71, lastModifiedTime=1710832993131, largestRecordTimestamp=1710832992125) due to log retention time 1000ms breach based on the largest record timestamp in the segment (kafka.log.UnifiedLog)
{code}
The segment is rolled due to log retention time 1000ms breached, which is unexpected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)