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 2020/02/18 08:01:00 UTC

[jira] [Updated] (HBASE-23864) No need to submit SplitTableRegionProcedure/MergeTableRegionsProcedure when split/merge is disabled

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

Guanghao Zhang updated HBASE-23864:
-----------------------------------
    Summary: No need to submit SplitTableRegionProcedure/MergeTableRegionsProcedure when split/merge is disabled  (was: No need to submit SplitTableRegionProcedure/MergeTableRegionsProcedure when split/merge switch is disabled)

> No need to submit SplitTableRegionProcedure/MergeTableRegionsProcedure when split/merge is disabled
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-23864
>                 URL: https://issues.apache.org/jira/browse/HBASE-23864
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Guanghao Zhang
>            Priority: Major
>         Attachments: HBASE-23864.PNG
>
>
> Now even the split/merge is disabled, master will submit a SplitTableRegionProcedure, too. And rollback it when execute failed. I thought the split/merge switch is a cluster level swtich. Master can check it early and no need to submit SplitTableRegionProcedure/MergeTableRegionsProcedure when split/merge switch is disabled.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)