[
https://issues.apache.org/jira/browse/KAFKA-6208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Harris resolved KAFKA-6208.
--------------------------------
Fix Version/s: 3.6.0
Resolution: Fixed
This is fixed by setting plugin.discovery=service_load on 3.6+, see
KAFKA-14627/KIP-898 for more details.
> Reduce startup time for Kafka Connect workers
> ---------------------------------------------
>
> Key: KAFKA-6208
> URL: https://issues.apache.org/jira/browse/KAFKA-6208
> Project: Kafka
> Issue Type: Improvement
> Components: connect
> Affects Versions: 1.0.0
> Reporter: Randall Hauch
> Priority: Major
> Labels: needs-kip
> Fix For: 3.6.0
>
>
> Kafka Connect startup times are excessive with a handful of connectors on the
> plugin path or classpath. We should not be scanning three times (once for
> connectors, once for SMTs, and once for converters), and hopefully we can
> avoid scanning directories that are clearly not plugin directories.
> We should also consider using Java's Service Loader to quickly identify
> connectors. The latter would require a KIP and would require time to for
> connectors to migrate, but we could be smarter about only scanning plugin
> directories that need to be scanned.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
