[jira] [Comment Edited] (KAFKA-17360) local log retention ms/bytes "-2" is not treated correctly

["Chia-Ping Tsai (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-17360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876390#comment-17876390 ] 

Chia-Ping Tsai edited comment on KAFKA-17360 at 8/24/24 12:11 AM:
------------------------------------------------------------------

[~cmccabe] this bug affects 3.8 and earlier indeed. I don’t mentioned the earlier branches because I am not sure whether there are patch releasees in the future. Another reason is this ticket includes “two” fixes - 1) the incorrect flag of “remote enable” is not existent in earlier branches. 2) By contrast, the fix of incorrect retention.xx does affect previous version.

I will open another ticket to backport only fix_2 to earlier branches after this gets resolved.

 

 

 


was (Author: chia7712):
[~cmccabe] this bug affects 3.8 and earlier indeed. I don’t mentioned the earlier branches because I am not sure whether there are patch releasees in the future. Another reason is this ticket includes “two” fixes - 1) the incorrect flag of “remote enable” may be not existent in earlier branches. 2) By contrast, the fix of incorrect retention.xx does affect previous version.

I will open another ticket to backport only fix_2 to earlier branches after this gets resolved.

 

 

 

> local log retention ms/bytes "-2" is not treated correctly
> ----------------------------------------------------------
>
>                 Key: KAFKA-17360
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17360
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Luke Chen
>            Assignee: Kuan Po Tseng
>            Priority: Critical
>             Fix For: 4.0.0, 3.9.0
>
>
> # When the local.retention.ms/bytes is set to -2, we didn't replace it with the server-side retention.ms/bytes config, so the -2 local retention won't take effect.
>  # When setting retention.ms/bytes to -2, we can notice this log message:
> {code:java}
> Deleting segment LogSegment(baseOffset=10045, size=1037087, lastModifiedTime=1724040653922, largestRecordTimestamp=1724040653835) due to local log retention size -2 breach. Local log size after deletion will be 13435280. (kafka.log.UnifiedLog) [kafka-scheduler-6]{code}
> This is not helpful for users. We should replace -2 with real retention value when logging.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)