[HDDS-3367] Trash Support for Ozone FileSystem

• Type: New Feature
• Status: Patch Available
• Priority: Blocker
• Resolution: Unresolved
• Affects Version/s: 1.0.0
• Component/s: Ozone Filesystem
• Labels: non_1.4.0_blocker
• Target Version/s: 1.3.0
• Assignee: Sadanand Shenoy
• Reporter: Sadanand Shenoy
• Created: 09/Apr/20 08:54
• Updated: 30/Aug/23 13:14

Description

The aim of this jira to add the trash feature capability in ozone that will help prevent accidental deletion of files and directories. When a file gets deleted in Ozone, the file is not immediately expelled from Ozone but will be moved to trash. Similarly as in HDFS, to immediately delete a file, a skipTrash option will be provided. The jira also aims to integrate the Ozone FS Trash to the Trash API developed as a part of HDDS-2416.

Issue Links

• depends upon: HDDS-3705 [OFS] Implement getTrashRoots for trash cleanup
• depends upon: HDDS-2416 Ozone Trash Feature
• is duplicated by: HDDS-2416 Ozone Trash Feature

Sub-Tasks

• Start Trash Emptier in Ozone Manager: Resolved
• Ozone specific TrashPolicy: Resolved
• Make Ozone specific Trash remover multi threaded: Resolved
• Handle start & stop of Trash Emptier thread when node becomes leader/follower: Resolved
• Move OFSPath to a common package to be used by the TrashFileSystem.: Resolved
• OM failed to start because trash emptier complains No FileSystem for scheme "ofs": Resolved
• Create a Trash File System that will be used by Trash Emptier: Resolved
• Write integration tests around Ozone trash remover: Resolved
• Disable Rocksdb caching when performing Trash specific operations: Resolved
• Add unit test around HA handling of Trash emptier: Open
• Add metrics around Trash Operations: Resolved
• Performance evaluation for Ozone trash emptier: Open
• Ozone specific undelete: Open
• TestOzoneFileSystem#testTrash() fails when OM Ratis is enabled: Resolved
• Define Ozone specific trash-interval and checkpoint interval: Resolved