[
https://issues.apache.org/jira/browse/KAFKA-13610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TengYao Chi updated KAFKA-13610:
--------------------------------
Fix Version/s: 5.0.0
> 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
> Labels: need-kip
> Fix For: 5.0.0
>
>
> 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)
