[
https://issues.apache.org/jira/browse/KAFKA-16414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831161#comment-17831161
]
Kamal Chandraprakash commented on KAFKA-16414:
----------------------------------------------
I noticed the behavior change of {{retention.ms}} and {{retention.bytes}} while
working on tiered storage integration tests. The behavior suited our
requirement for integration tests where we want to keep only the active segment
locally and move all the passive segments to remote storage.
If we update the behavior, then it will make most of the tiered storage tests
flaky, as all the segments will be rotated and uploaded to remote. And, the
local segment will be empty. We also have to update the tiered storage
integration tests when changing the behavior of the {{retention.bytes}} config.
https://sourcegraph.com/github.com/apache/kafka@932647606504125e5c3ba0ae9470b4af335a0885/-/blob/storage/src/test/java/org/apache/kafka/tiered/storage/utils/TieredStorageTestUtils.java?L174
> 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
> Priority: Major
>
> 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)
