You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/01/07 19:09:00 UTC
[jira] [Resolved] (KAFKA-9330) Calling AdminClient.close in the
AdminClient completion callback causes deadlock
[ https://issues.apache.org/jira/browse/KAFKA-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Gustafson resolved KAFKA-9330.
------------------------------------
Fix Version/s: 2.5.0
Resolution: Fixed
> Calling AdminClient.close in the AdminClient completion callback causes deadlock
> --------------------------------------------------------------------------------
>
> Key: KAFKA-9330
> URL: https://issues.apache.org/jira/browse/KAFKA-9330
> Project: Kafka
> Issue Type: Bug
> Reporter: Vikas Singh
> Assignee: Vikas Singh
> Priority: Major
> Fix For: 2.5.0
>
>
> The close method calls `Thread.join` to wait for AdminClient thread to die, but that doesn't happen as the thread calling join is the AdminClient thread. This causes the thread to block forever, causing a deadlock where it forever waits for itself to die.
> `AdminClient.close` should check if the thread calling close is same as current thread, then skip the join. The thread will check for close condition in the main loop and exit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)