You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "TengYao Chi (Jira)" <ji...@apache.org> on 2025/03/22 16:11:00 UTC

[jira] [Assigned] (KAFKA-13610) Make log.cleaner.enable dynamically configurable

     [ https://issues.apache.org/jira/browse/KAFKA-13610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

TengYao Chi reassigned KAFKA-13610:
-----------------------------------

    Assignee: TengYao Chi

> Make log.cleaner.enable dynamically configurable
> ------------------------------------------------
>
>                 Key: KAFKA-13610
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13610
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Colin McCabe
>            Assignee: TengYao Chi
>            Priority: Major
>
> It's odd that things like the number of log cleaner threads are configurable, but not whether it is on or off. We should make log.cleaner.enable dynamically configurable to close this gap.
> Additionally, from a code point of view, we should unconditionally create the log cleaner object in the LogManager constructor even if we never start it. This would simplify the code and eliminate many null checks.



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