[ 
https://issues.apache.org/jira/browse/KAFKA-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214685#comment-17214685
 ] 

Goltseva Taisiia edited comment on KAFKA-7421 at 10/15/20, 1:30 PM:
--------------------------------------------------------------------

Hi, [~kleiby] !

Let me describe my issue more detailed. Maybe we will be able to figure out 
some similar details with you which causing the problem.

We have a base docker image containing several connectors (each connector in a 
separate folder under /plugins folder). And one custom converter in /libs. And 
this docker image works perfect, never such deadlocks.

Also we have a child docker image which adds additional connector in a separate 
folder under /plugins folder. And several additional custom converters in the 
same folder! We cannot put them in /libs folder currently, but I will try to do 
it. And this docker image get this deadlock very often.

Several custom converters in the same folder with a connector is the only 
difference with the approach of our base docker image. So, I suppose maybe this 
cause our deadlocks. But I'm not sure, I will try to separate converters and 
see.

 

Can you describe your configuration also& Maybe there are some similarities 
with us? Do you have SMTs or converters in one folder, in one jar?


was (Author: xakassi):
Hi, [~kleiby] !

Let me describe my issue more detailed. Maybe we will be able to figure out 
some similar details with you which causing the problem.

We have a base docker image containing several connector (each connector in a 
separate folder under /plugins folder). And one custom converter in /libs. And 
this docker image works perfect, never such deadlocks.

Also we have a child docker image which adds additional connector in a separate 
folder under /plugins folder. And several additional custom converters in the 
same folder! We cannot put them in /libs folder currently, but I will try to do 
it. And this docker image get this deadlock very often.

Several custom converters in the same folder with a connector is the only 
difference with the approach of our base docker image. So, I suppose maybe this 
cause our deadlocks. But I'm not sure, I will try to separate converters and 
see.

 

Can you describe your configuration also& Maybe there are some similarities 
with us? Do you have SMTs or converters in one folder, in one jar?

> Deadlock in Kafka Connect
> -------------------------
>
>                 Key: KAFKA-7421
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7421
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 2.0.0
>            Reporter: Maciej Bryński
>            Assignee: Konstantine Karantasis
>            Priority: Major
>
> I'm getting this deadlock on half of Kafka Connect runs when having two 
> different types connectors (in this configuration it's debezium and hdfs).
> Thread 1:
> {code}
> "pool-22-thread-2@4748" prio=5 tid=0x4d nid=NA waiting for monitor entry
>   java.lang.Thread.State: BLOCKED
>        waiting for pool-22-thread-1@4747 to release lock on <0x1423> (a 
> org.apache.kafka.connect.runtime.isolation.PluginClassLoader)
>         at 
> org.apache.kafka.connect.runtime.isolation.PluginClassLoader.loadClass(PluginClassLoader.java:91)
>         at 
> org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:367)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>         at java.lang.Class.forName0(Class.java:-1)
>         at java.lang.Class.forName(Class.java:348)
>         at 
> org.apache.kafka.common.config.ConfigDef.parseType(ConfigDef.java:715)
>         at 
> org.apache.kafka.connect.runtime.ConnectorConfig.enrich(ConnectorConfig.java:295)
>         at 
> org.apache.kafka.connect.runtime.ConnectorConfig.<init>(ConnectorConfig.java:200)
>         at 
> org.apache.kafka.connect.runtime.ConnectorConfig.<init>(ConnectorConfig.java:194)
>         at 
> org.apache.kafka.connect.runtime.Worker.startConnector(Worker.java:233)
>         at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder.startConnector(DistributedHerder.java:916)
>         at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder.access$1300(DistributedHerder.java:111)
>         at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder$15.call(DistributedHerder.java:932)
>         at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder$15.call(DistributedHerder.java:928)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
> {code}
> Thread 2:
> {code}
> "pool-22-thread-1@4747" prio=5 tid=0x4c nid=NA waiting for monitor entry
>   java.lang.Thread.State: BLOCKED
>        blocks pool-22-thread-2@4748
>        waiting for pool-22-thread-2@4748 to release lock on <0x1421> (a 
> org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:406)
>         at 
> org.apache.kafka.connect.runtime.isolation.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:358)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:411)
>         - locked <0x1424> (a java.lang.Object)
>         at 
> org.apache.kafka.connect.runtime.isolation.PluginClassLoader.loadClass(PluginClassLoader.java:104)
>         - locked <0x1423> (a 
> org.apache.kafka.connect.runtime.isolation.PluginClassLoader)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>         at 
> io.debezium.transforms.ByLogicalTableRouter.<clinit>(ByLogicalTableRouter.java:57)
>         at java.lang.Class.forName0(Class.java:-1)
>         at java.lang.Class.forName(Class.java:348)
>         at 
> org.apache.kafka.common.config.ConfigDef.parseType(ConfigDef.java:715)
>         at 
> org.apache.kafka.connect.runtime.ConnectorConfig.enrich(ConnectorConfig.java:295)
>         at 
> org.apache.kafka.connect.runtime.ConnectorConfig.<init>(ConnectorConfig.java:200)
>         at 
> org.apache.kafka.connect.runtime.ConnectorConfig.<init>(ConnectorConfig.java:194)
>         at 
> org.apache.kafka.connect.runtime.Worker.startConnector(Worker.java:233)
>         at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder.startConnector(DistributedHerder.java:916)
>         at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder.access$1300(DistributedHerder.java:111)
>         at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder$15.call(DistributedHerder.java:932)
>         at 
> org.apache.kafka.connect.runtime.distributed.DistributedHerder$15.call(DistributedHerder.java:928)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>         at java.lang.Thread.run(Thread.java:748)
> {code}
> I'm using official Confluent Docker images.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to