You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Jide (Jira)" <ji...@apache.org> on 2026/04/01 17:01:00 UTC

[jira] [Commented] (HBASE-30049) RestoreSnapshotHelper creates StoreFileTracker with wrong config causing no-op filelist updates

    [ https://issues.apache.org/jira/browse/HBASE-30049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18070386#comment-18070386 ] 

Jide commented on HBASE-30049:
------------------------------

Thanks for the review and comments [~prathyu6]. Updated the PR

> RestoreSnapshotHelper creates StoreFileTracker with wrong config causing no-op filelist updates
> -----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-30049
>                 URL: https://issues.apache.org/jira/browse/HBASE-30049
>             Project: HBase
>          Issue Type: Bug
>          Components: snapshots
>            Reporter: Jide
>            Priority: Major
>              Labels: pull-request-available
>
> RestoreSnapshotHelper.restoreRegion() creates a StoreFileTracker using the raw Master configuration, which lacks the table-level hbase.store.file-tracker.impl=FILE setting. This causes StoreFileTrackerFactory.create() to resolve to DefaultStoreFileTracker, whose doSetStoreFiles() is a no-op, meaning the .filelist is never updated after the restore moves HFiles to archive. When the table is subsequently read, RegionServers attempt to open files listed in the stale .filelist that have already been archived, resulting in FileNotFoundException. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)