[
https://issues.apache.org/jira/browse/HBASE-20659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495451#comment-16495451
]
Hudson commented on HBASE-20659:
--------------------------------
Results for branch branch-2
[build #802 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/802/]:
(/) *{color:green}+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/802//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/802//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/802//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Implement a reopen table regions procedure
> ------------------------------------------
>
> Key: HBASE-20659
> URL: https://issues.apache.org/jira/browse/HBASE-20659
> Project: HBase
> Issue Type: Bug
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20659.patch
>
>
> For serial replication peer, and sync replication peer on branch HBASE-19064,
> sometimes we need to reopen the regions for a table to make sure that we have
> some wal edits which have not been replicated yet, or let the region switch a
> wal implementation. But for peer related procedures, we do not hold the table
> lock so if there are region split or merge than we may fail to reopen all the
> regions and cause problems.
> So I think we need to introduce a table procedure which is used to reopen all
> the regions for a table, and like other table procedures, such as
> ModifyTableProcedure, it will hold the exclusive lock on a table so we will
> not miss the new regions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
