You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Kuan Po Tseng (Jira)" <ji...@apache.org> on 2024/06/25 09:44:00 UTC

[jira] [Commented] (KAFKA-17035) Add debug log to retention cleanupLogs method to help troubleshoot issues

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

Kuan Po Tseng commented on KAFKA-17035:
---------------------------------------

Hi [~showuon] , I think I can help on this one, could you assign to me ? Many thanks~

> Add debug log to retention cleanupLogs method to help troubleshoot issues
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-17035
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17035
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Luke Chen
>            Priority: Major
>
> Sometimes, there will be some log segments leftover without getting deleted as configured. One example is, the config is set to retention.ms = 7 days, but there are some log segments stay in storage for more than 7 days. In this case, it's difficult to troubleshoot if there is a bug in kafka or something wrong in the log segment (ex: max time is wrongly set).
> To help troubleshooting, we could add "trace level" or "debug level" logs when doing retentionSize/retentionMs/logStartOffset check for each log segment.



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