kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guozhang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-5451) Kafka Connect should scan classpath asynchronously
Date Sat, 23 Sep 2017 04:28:19 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Guozhang Wang updated KAFKA-5451:
---------------------------------
    Fix Version/s:     (was: 1.0.0)
                   1.1.0

> 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
>              Labels: performance
>             Fix For: 1.1.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
(v6.4.14#64029)

Mime
View raw message