[
https://issues.apache.org/jira/browse/HBASE-30137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078649#comment-18078649
]
Wellington Chevreuil commented on HBASE-30137:
----------------------------------------------
Maybe a duplicate of
[HBASE-26624|https://issues.apache.org/jira/browse/HBASE-26624]?
> In FSFT, generate a new manifest incase the latest manifest file gets
> corrupted
> -------------------------------------------------------------------------------
>
> Key: HBASE-30137
> URL: https://issues.apache.org/jira/browse/HBASE-30137
> Project: HBase
> Issue Type: Improvement
> Reporter: Prathyusha
> Priority: Major
>
> Add an offline recovery mechanism for corrupted FILE store file tracker
> manifest .
> The repair should support a minimal {{disk-only}} mode that rebuilds manifest
> contents from the child family directory, and a {{lineage-assisted}} mode
> that augments those files by simulating split/merge parent artifacts when
> current {{hbase:meta}} still proves lineage.
> The should write a fresh manifest generation instead of modifying the
> corrupted manifest in place, and support dry-run for safe operator use.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
