You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2026/09/27 05:46:00 UTC
[jira] [Updated] (HBASE-30352) Tolerate stale recovered.edits below durable seqid in split/merge
[ https://issues.apache.org/jira/browse/HBASE-30352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Viraj Jasani updated HBASE-30352:
---------------------------------
Summary: Tolerate stale recovered.edits below durable seqid in split/merge (was: MergeTableRegionsProcedure/SplitTableRegionProcedure: tolerate stale recovered.edits below durable seqid)
> 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
>
> {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)