You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Greg Harris (Jira)" <ji...@apache.org> on 2021/03/08 17:49:00 UTC
[jira] [Updated] (KAFKA-9186) Kafka Connect floods logs with
probably bogus error messages from DelegatingClassLoader
[ https://issues.apache.org/jira/browse/KAFKA-9186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Harris updated KAFKA-9186:
-------------------------------
Fix Version/s: 2.5.0
3.0.0
> Kafka Connect floods logs with probably bogus error messages from DelegatingClassLoader
> ---------------------------------------------------------------------------------------
>
> Key: KAFKA-9186
> URL: https://issues.apache.org/jira/browse/KAFKA-9186
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.3.1
> Reporter: Piotr Szczepanik
> Priority: Minor
> Fix For: 3.0.0, 2.5.0
>
>
> After upgrading Kafka Connect from 2.3.0 to 2.3.1 we discovered a lot of recurring ERROR messages in Connect's logs.
> {noformat}
> Plugin class loader for connector: 'com.google.pubsub.kafka.sink.CloudPubSubSinkConnector' was not found. Returning: org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader@58f437b0
> logger: org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader
> {noformat}
> Kafka Connect continues processing the topics as it should be.
> We are not using plugin classloader isolation feature by not specifying plugin.path property because we were seeing classloading deadlocks similar to ones described in [KAFKA-7421|https://issues.apache.org/jira/browse/KAFKA-7421]
> Maybe the level of this message should be lowered?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)