[
https://issues.apache.org/jira/browse/HBASE-22061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796838#comment-16796838
]
Jingyun Tian commented on HBASE-22061:
--------------------------------------
Pushed to master, branch-2 and branch-2.2, thanks [~allan163] for reviewing.
> 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)
