You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Piotr Szczepanik (Jira)" <ji...@apache.org> on 2019/11/14 12:20:00 UTC

[jira] [Created] (KAFKA-9186) Kafka Connect floods logs with probably bogus error messages from DelegatingClassLoader

Piotr Szczepanik created KAFKA-9186:
---------------------------------------

             Summary: 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


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)