[
https://issues.apache.org/jira/browse/HBASE-22922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917161#comment-16917161
]
Hudson commented on HBASE-22922:
--------------------------------
Results for branch master
[build #1364 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1364/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/master/1364//console].
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/master/1364//console].
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/master/1364//console].
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Only the two first regions are locked in MergeTableRegionsProcedure
> -------------------------------------------------------------------
>
> Key: HBASE-22922
> URL: https://issues.apache.org/jira/browse/HBASE-22922
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.2.1
> Reporter: István Tóth
> Assignee: István Tóth
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2
>
>
> After the recent multi-region merge rewrite, the locking methods in
> MergeTableRegionsProcedure are called only for the first two regions to be
> merged.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
