[
https://issues.apache.org/jira/browse/HBASE-22354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832289#comment-16832289
]
Hudson commented on HBASE-22354:
--------------------------------
Results for branch branch-2
[build #1863 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1863/]:
(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/1863//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1863//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1863//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> master never sets abortRequested, and thus abort timeout doesn't work for it
> ----------------------------------------------------------------------------
>
> Key: HBASE-22354
> URL: https://issues.apache.org/jira/browse/HBASE-22354
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-22354.patch
>
>
> Discovered w/HBASE-22353 netty deadlock.
> The property is not set, so the abort timer is not started.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
