[
https://issues.apache.org/jira/browse/KAFKA-16552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-16552.
------------------------------------
Fix Version/s: 3.8.0
Resolution: Fixed
> Create an internal config to control InitialTaskDelayMs in LogManager to
> speed up tests
> ---------------------------------------------------------------------------------------
>
> Key: KAFKA-16552
> URL: https://issues.apache.org/jira/browse/KAFKA-16552
> Project: Kafka
> Issue Type: Improvement
> Reporter: Luke Chen
> Assignee: Kuan Po Tseng
> Priority: Major
> Fix For: 3.8.0
>
>
> When startup LogManager, we'll create schedule tasks like:
> kafka-log-retention, kafka-recovery-point-checkpoint threads...etc
> ([here|https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/log/LogManager.scala#L629]).
> All of them have public configs to configure the interval, like
> `log.retention.check.interval.ms`. But in addition to the scheduler interval,
> there's a hard coded InitialTaskDelayMs (30 seconds) for all of them. That
> might not be a problem in production env, since it'll make the kafka server
> start up faster. But in test env, the 30 secs delay means if there are tests
> verifying the behaviors like log retention, it'll take 30 secs up to complete
> the tests.
> To speed up tests, we should create an internal config (ex:
> "log.initial.task.delay.ms") to control InitialTaskDelayMs in LogManager to
> speed up tests. This is not intended to be used by normal users, just for
> speeding up testing usage.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
