gvprathyusha6 commented on code in PR #8382: URL: https://github.com/apache/hbase/pull/8382#discussion_r3592914323
########## dev-support/design-docs/fsft-manifest-recover.md: ########## @@ -0,0 +1,268 @@ +# FSFT Manifest Recover Design + +## Problem + +The FILE store file tracker (FSFT) persists store membership in manifest files under `.filelist`. +If the newest manifest is corrupted in a non-EOF way, `StoreFileListFile.load(...)` fails hard and +region/store open can fail as well. + +For FILE SFT, the manifest can in principle reference store members that do not exist as plain +files in the child family directory: + +- plain HFiles do exist on disk +- virtual split/merge `Reference`s may exist only in the manifest +- virtual `HFileLink`s may exist only in the manifest plus archive back references + +This design adds a single, offline, operator-driven recovery tool that rebuilds a corrupted +manifest **purely from the store directory listing**, plus a non-authoritative data-loss assessment +derived from `hbase:meta` split/merge lineage. Review Comment: Yes, but incase the archival of parents is done by process links/references are already compacted so no data loss in that scenario, else there is scope of data loss similar to a corrupted HFile -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
