You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2019/04/28 00:54:00 UTC

[jira] [Updated] (HBASE-22061) SplitTableRegionProcedure should hold the lock of its daughter regions

     [ https://issues.apache.org/jira/browse/HBASE-22061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guanghao Zhang updated HBASE-22061:
-----------------------------------
    Fix Version/s:     (was: 2.2.1)
                   2.2.0

> 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.2.0
>
>         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)