[
https://issues.apache.org/jira/browse/KAFKA-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Harris resolved KAFKA-5451.
--------------------------------
Resolution: Won't Do
Kafka Connect needs the results of plugin scanning to answer basic REST
queries, and to be assigned workloads via joining the group. Without finalized
scan results, neither of these operations can meaningfully complete.
Rather than make the scanning asynchronous, we have elected to make it faster
via KAFKA-14627/KIP-898. It no longer makes sense to async-process something
that takes <1s.
> Kafka Connect should scan classpath asynchronously
> --------------------------------------------------
>
> Key: KAFKA-5451
> URL: https://issues.apache.org/jira/browse/KAFKA-5451
> Project: Kafka
> Issue Type: Improvement
> Components: connect
> Affects Versions: 0.11.0.0
> Reporter: Randall Hauch
> Assignee: Randall Hauch
> Priority: Major
> Labels: performance
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> When Kafka Connect workers start up, they scan the classpath and module paths
> for connectors, transformations, and converters. This takes anywhere from
> 15-30sec or longer depending upon how many JARs are included. Currently, this
> scanning is done synchronously during startup of the Kafka Connect workers,
> even though the workers may not need the result of the scan.
> The scanning logic should be asynchronous and should only block any
> components that require the result of the scan. This will improve startup
> time of the workers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
