Description
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.
Attachments
Issue Links
- is related to
-
KAFKA-6503 Connect: Plugin scan is very slow
-
- Resolved
-
- relates to
-
KAFKA-14627 Modernize Connect plugin discovery
-
- Resolved
-
-
KAFKA-5451 Kafka Connect should scan classpath asynchronously
-
- Open
-