[
https://issues.apache.org/jira/browse/KAFKA-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635600#comment-16635600
]
Dong Lin commented on KAFKA-5451:
---------------------------------
Moving this to 2.2.0 since PR is not ready yet.
> Kafka Connect should scan classpath asynchronously
> --------------------------------------------------
>
> Key: KAFKA-5451
> URL: https://issues.apache.org/jira/browse/KAFKA-5451
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 0.11.0.0
> Reporter: Randall Hauch
> Assignee: Randall Hauch
> Priority: Major
> Labels: performance
> Fix For: 2.2.0
>
> 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
(v7.6.3#76005)
