[
https://issues.apache.org/jira/browse/HBASE-25835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339387#comment-17339387
]
Hudson commented on HBASE-25835:
--------------------------------
Results for branch branch-2
[build #241 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/241/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/241/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/241/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/241/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/241/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Ignore duplicate split requests from regionserver reports
> ---------------------------------------------------------
>
> Key: HBASE-25835
> URL: https://issues.apache.org/jira/browse/HBASE-25835
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.4.3
> Reporter: Andrew Kyle Purtell
> Assignee: Andrew Kyle Purtell
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3
>
>
> A SplitTableRegionProcedure may already be running when a regionserver report
> is received that includes a split request. The outcome is multiple
> SplitTableRegionProcedure procedures scheduled for the split request, only
> one of which can succeed. The others error out. Perhaps it is only WARN level
> noise in the logs that will cause operator concern, but is clearly not
> correct.
> Do not create a split procedure in response to a region state change report
> if the region is not open or already splitting.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
