[
https://issues.apache.org/jira/browse/HBASE-23864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040638#comment-17040638
]
Michael Stack commented on HBASE-23864:
---------------------------------------
Or here in branch-2
https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2/lastSuccessfulBuild/artifact/dashboard.html
See second set of tests in all cases.
> 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
> Assignee: Guanghao Zhang
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.4, 2.1.10
>
> 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)
