[
https://issues.apache.org/jira/browse/HBASE-22061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797108#comment-16797108
]
Hudson commented on HBASE-22061:
--------------------------------
Results for branch master
[build #872 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/872/]: (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/master/872//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/master/872//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/master/872//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> SplitTableRegionProcedure should hold the lock of its daughter regions
> ----------------------------------------------------------------------
>
> Key: HBASE-22061
> URL: https://issues.apache.org/jira/browse/HBASE-22061
> Project: HBase
> Issue Type: Bug
> Reporter: Jingyun Tian
> Assignee: Jingyun Tian
> Priority: Major
> Fix For: 3.0.0, 2.1, 2.2
>
> Attachments: HBASE-22061.master.001.patch,
> HBASE-22061.master.002.patch
>
>
> Currently SplitTableRegionProcedure only hold the region of parent region.
> But during processing of this procedure, after the daughter regions are
> updated to meta, other procedures can grab the lock of them, which is the
> situation we don't want to see.
> So I think SplitTableRegionProcedure should hold the lock of parent region
> and its daughter regions like MergeTableRegionsProcedure holding the lock of
> merged region.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
