Kuan Po Tseng created KAFKA-16414: ------------------------------------- Summary: Inconsistent active segment expiration behavior between retention.ms and retention.bytes Key: KAFKA-16414 URL: https://issues.apache.org/jira/browse/KAFKA-16414 Project: Kafka Issue Type: Improvement Affects Versions: 3.6.1 Reporter: Kuan Po Tseng Assignee: Kuan Po Tseng
This is a follow up issue on KAFKA-16385. Currently, there's a difference between how retention.ms and retention.bytes handle active segment expiration: - retention.ms always expire active segment when max segment timestamp matches the condition. - retention.bytes only expire active segment when retention.bytes is configured to zero. The behavior should be either rotate active segments for both retention configurations or none at all. For more details, see https://issues.apache.org/jira/browse/KAFKA-16385?focusedCommentId=17829682&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17829682 -- This message was sent by Atlassian Jira (v8.20.10#820010)