[
https://issues.apache.org/jira/browse/HBASE-24506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128695#comment-17128695
]
Hudson commented on HBASE-24506:
--------------------------------
Results for branch branch-2.2
[build #888 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/888/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/888//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/888//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/888//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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)
