[
https://issues.apache.org/jira/browse/HBASE-22061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jingyun Tian updated HBASE-22061:
---------------------------------
Description:
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.
was:
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.
> 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
> Priority: Major
>
> 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)
