[
https://issues.apache.org/jira/browse/HBASE-20514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461924#comment-16461924
]
Hudson commented on HBASE-20514:
--------------------------------
Results for branch branch-2
[build #688 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/688/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/688//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/688//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/688//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> On Master restart if table is stuck in DISABLING state, CLOSED regions should
> not be considered stuck in-transition
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-20514
> URL: https://issues.apache.org/jira/browse/HBASE-20514
> Project: HBase
> Issue Type: Bug
> Components: amv2
> Affects Versions: 2.0.0
> Reporter: Umesh Agashe
> Assignee: Umesh Agashe
> Priority: Major
> Fix For: 2.0.1
>
> Attachments: hbase-20514.master.001.patch
>
>
> When master is restarted, in AssignmentManager#loadMeta(), if table is in
> DISABLED state nothing is done for regions in CLOSED state. But if table is
> stuck in DISABLING state then CLOSED regions are considered as stuck
> in-transition. CLOSED regions of DISABLING/ DISABLED table can be handled the
> same way.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
