[
https://issues.apache.org/jira/browse/HBASE-26383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432665#comment-17432665
]
Hudson commented on HBASE-26383:
--------------------------------
Results for branch branch-2
[build #371 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/371/]:
(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/371/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/371/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/371/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/371/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/371//console].
> HBCK incorrectly reports inconsistencies for recently split regions following
> a master failover
> -----------------------------------------------------------------------------------------------
>
> Key: HBASE-26383
> URL: https://issues.apache.org/jira/browse/HBASE-26383
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 2.4.3
> Reporter: Benoit Sigoure
> Assignee: Andrew Kyle Purtell
> Priority: Critical
> Fix For: 2.5.0, 3.0.0-alpha-2, 2.4.8
>
>
> When a region P splits into A and B, following a master failover the newly
> active master reports that P is in an inconsistent state. This seems to be a
> regression introduced in HBASE-25847 (cc [[email protected]]) which
> changed {{regionInfo.isParentSplit()}} to {{regionState.isSplit()}}. The
> region state after restart is CLOSED (rather than SPLIT), so both region
> state and region info should be checked, presumably with
> {{regionState.isSplit() || regionInfo.isSplit()}}. This situation resolves
> itself on its own when a major compaction occurs and P is GCed, but having
> the master incorrectly report inconsistencies is pretty bad. We had a pretty
> big outage due to a series of operator errors as our SRE team was trying to
> fix this inconsistency that, in fact, didn't even exist.
> Thanks to Stack for helping look over this issue and Vlad Hanciuta for root
> causing the bug.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
