[
https://issues.apache.org/jira/browse/HBASE-23864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040284#comment-17040284
]
Hudson commented on HBASE-23864:
--------------------------------
Results for branch branch-2
[build #2487 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2487/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2487//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2487//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2487//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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)
