sarvekshayr opened a new pull request, #8955: URL: https://github.com/apache/ozone/pull/8955
## What changes were proposed in this pull request? Fixed logic - - `FSORepairTool` now uses two temporary RocksDB tables one for reachable and one for unreachable entries. - The reachable table stores objectID based keys (/volumeID/bucketID/objectID) for all objects accessible via DFS traversal from the bucket root. - The unreachable table stores original directory/file keys (/volumeID/bucketID/parentID/name) for objects whose ancestors are pending deletion in the `deletedDirectoryTable`. - `isReachable()` performs a parent based lookup to check if an object's parent exists in the reachable table, while `isUnreachable()` performs a direct key lookup in the unreachable table. - Objects that are neither reachable nor unreachable are classified as unreferenced and marked for repair. - Unreachable objects are not marked for repair as background cleanup processes will eventually handle them. - To be clear, included what unreachable and unreferenced mean in brackets of the final report. ``` "Reachable:" + reachable + "\nUnreachable (Pending to delete):" + unreachable + "\nUnreferenced (Orphaned):" + unreferenced; ``` ## What is the link to the Apache JIRA [HDDS-13549](https://issues.apache.org/jira/browse/HDDS-13549) ## How was this patch tested? Added a test `testUnreachableObjectsWithParentInDeletedTable` in `TestFSORepairTool` to verify unreachable objects. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
