You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2020/06/08 02:22:00 UTC

[jira] [Resolved] (HBASE-24506) async client deadlock

     [ https://issues.apache.org/jira/browse/HBASE-24506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Duo Zhang resolved HBASE-24506.
-------------------------------
    Hadoop Flags: Reviewed
      Resolution: Fixed

Pushed to branch-2.2+.

Thanks all for reviewing.

Thanks [~whitney13] for reporting this critical problem.

> async client deadlock
> ---------------------
>
>                 Key: HBASE-24506
>                 URL: https://issues.apache.org/jira/browse/HBASE-24506
>             Project: HBase
>          Issue Type: Bug
>          Components: asyncclient
>    Affects Versions: 3.0.0-alpha-1, 2.3.0, 2.2.4, 2.4.0, 2.2.5
>            Reporter: Whitney Jackson
>            Assignee: Duo Zhang
>            Priority: Blocker
>             Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> 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)