[
https://issues.apache.org/jira/browse/KAFKA-16414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875799#comment-17875799
]
Jorge Esteban Quilcate Otoya commented on KAFKA-16414:
------------------------------------------------------
Back on this one, I think now it's a good chance to make a change towards 4.0
and avoid having this inconsistency between retention configurations.
I see there's some agreement on aligning these configs, but my guess is that
any further change would require a KIP.
A proposal to align these should outline a couple of alternatives at least:
First:
* retention.bytes will rotate active segment if the condition is breached.
* local.retention.bytes will inherit this behavior as well, and rotate active
segment.
* with these changes we could trigger active segment rotation either by using
roll.ms/segment.bytes or (local.)retention.(ms|bytes)
an second alternative:
* remove active segment rotation from local.retention.ms
* remove active segment rotation from retention.ms
* let roll.ms and segment.bytes be the configurations to trigger active
segment rotation
both unfortunately force changing some existing behavior and potentially
affecting users already counting on them.
Another alternative could be just leaving things as they are, but at least that
should be explicitly agreed and properly documented.
Personally, I'd prefer the second option. Would these be a good starting point
to start a KIP discussion?
> 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)
