[
https://issues.apache.org/jira/browse/HBASE-22360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835521#comment-16835521
]
Hudson commented on HBASE-22360:
--------------------------------
Results for branch branch-2
[build #1875 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1875/]:
(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/1875//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/1875//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/1875//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Abort timer doesn't set when abort is called during graceful shutdown process
> -----------------------------------------------------------------------------
>
> Key: HBASE-22360
> URL: https://issues.apache.org/jira/browse/HBASE-22360
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Bahram Chehrazy
> Assignee: Bahram Chehrazy
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: Set-the-abortMonitor-timer-in-the-abort-function-01.patch
>
>
> The abort timer only get set when the server is aborted. But if the server is
> being gracefully stopped and something goes wrong causing an abort, the timer
> may not get set, and the shutdown process could take a very long time or
> completely stuck the server.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
