[
https://issues.apache.org/jira/browse/KAFKA-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234265#comment-16234265
]
Rajini Sivaram commented on KAFKA-6155:
---------------------------------------
This deadlock has been fixed under KAFKA-5970 and KAFKA-6042. The fix is
included in the 1.0.0 release. The fixes have also been applied to the 0.11.0
branch in case you would like to try it out.
> Found Dead Lock Error on broker
> -------------------------------
>
> Key: KAFKA-6155
> URL: https://issues.apache.org/jira/browse/KAFKA-6155
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.11.0.0
> Reporter: Chengxiang Li
> Priority: Critical
> Attachments: 20890.txt
>
>
> During one of our test, we found that all the produce/consumer request to one
> of our kafka broker got timeout, and the server of this kafka broker holds
> more than 200K `CLOSE_WAIT` network connections and it grows continously.
> After research the jstack output of Kafka broker, we found a
> *{color:red}DeadLock{color}* and a Lock(0x00000005c109dd50) which waited by
> many thread and no one hold it. You can see the attached file for more detail.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
