[
https://issues.apache.org/jira/browse/HBASE-24506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126296#comment-17126296
]
Duo Zhang commented on HBASE-24506:
-----------------------------------
The problem here is that, in failInit, we will complete all the pending calls,
and these calls will call their callback handlers, and since then in these
handlers, we will do other things which will acquire the lock of a
RpcConnection again.
This maybe a common problem, not only for failInit. Let me think how to deal
with it.
Thanks for reporting.
> async client deadlock
> ---------------------
>
> Key: HBASE-24506
> URL: https://issues.apache.org/jira/browse/HBASE-24506
> Project: HBase
> Issue Type: Bug
> Components: asyncclient
> Affects Versions: 2.2.4
> Reporter: Whitney Jackson
> Priority: Major
>
> I ran into an issue where one instance in a cluster of application servers
> backed by HBase stopped processing requests. Looking at a thread dump, it
> seems HBase client threads are deadlocked:
> https://pastebin.com/raw/B3FJL1Ag
> The deadlock seemed to happen at the same time that a region server was
> abruptly stopped (the physical server was restarted unexpectedly).
> I'm using the hbase async API. The hbase client version is 2.2.4. The server
> is running 2.2.4 as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
