[
https://issues.apache.org/jira/browse/HBASE-30352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119814#comment-18119814
]
Hudson commented on HBASE-30352:
--------------------------------
Results for branch branch-3.0
[build #36 on
builds.a.o|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3.0/36/]:
(/) *{color:green}+1 overall{color}*
----
Backwards compatibility checks:
(/) {color:green}+1 jdk17 hadoop 3.3.5 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3.0/36/console]
(/) {color:green}+1 jdk17 hadoop 3.3.6 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3.0/36/console]
(/) {color:green}+1 jdk17 hadoop 3.4.0 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3.0/36/console]
(/) {color:green}+1 jdk17 hadoop 3.4.1 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3.0/36/console]
(/) {color:green}+1 jdk17 hadoop 3.4.2 backward compatibility checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase-Backwards-Compatibility-Test/job/branch-3.0/36/console]
> Tolerate stale recovered.edits below durable seqid in split/merge
> -----------------------------------------------------------------
>
> Key: HBASE-30352
> URL: https://issues.apache.org/jira/browse/HBASE-30352
> Project: HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 3.0.0, 2.5.16, 2.6.7
> Reporter: Nirdosh Kumar Yadav
> Assignee: Nirdosh Kumar Yadav
> Priority: Minor
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-1, 2.7.0, 3.1.0, 3.0.1, 2.6.8, 2.5.17
>
>
> {color:#172b4d}When MergeTableRegionsProcedure fails at the
> MERGE_TABLE_REGIONS_CHECK_CLOSED_REGIONS state — e.g. because
> AssignmentManagerUtil.checkClosedRegion() throws "Recovered.edits are found
> in Region: … abort split/merge to prevent data loss" — the procedure
> framework unwinds through rollbackState(). The
> MERGE_TABLE_REGIONS_CHECK_CLOSED_REGIONS case is a bare break;, so the
> parents that were CLOSED during the prior forward step
> MERGE_TABLE_REGIONS_CLOSE_REGIONS are never re-opened. Both parent regions
> remain OFFLINE and the RIT can persist indefinitely until an operator
> intervenes. So we will check the max seq ID of recovered edits and compare
> with max Seq ID of region and Ignore if recovered edits are stale. {color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
