[
https://issues.apache.org/jira/browse/HBASE-21330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655095#comment-16655095
]
Hudson commented on HBASE-21330:
--------------------------------
Results for branch branch-2
[build #1406 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/1406/]:
(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/1406//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/1406//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/1406//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> ReopenTableRegionsProcedure will enter an infinite loop if we schedule a TRSP
> at the same time
> ----------------------------------------------------------------------------------------------
>
> Key: HBASE-21330
> URL: https://issues.apache.org/jira/browse/HBASE-21330
> Project: HBase
> Issue Type: Sub-task
> Components: amv2
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-21330.patch
>
>
> The problem is that, if there are regions which already have TRSPs with them,
> we will give up and just to REOPEN_TABLE_REGIONS_CONFIRM_REOPENED directly.
> And in REOPEN_TABLE_REGIONS_CONFIRM_REOPENED, if there are still regions need
> to be reopened, we will just back to REOPEN_TABLE_REGIONS_REOPEN_REGIONS
> directly. And since ReopenTableRegionsProcedure holds the exclusive lock on
> table, the TRSP will not have chance to execute, and the result is that, the
> ReopenTableRegionsProcedure just keep looping in the two states.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)