[HDDS-7994] Expose information on keys marked for deletion and moved to the DeletedTable

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: Ozone Recon
• Labels: pull-request-available
• Assignee: Mohammad Arafat Khan
• Reporter: Mohammad Arafat Khan
• Created: 21/Feb/23 09:14
• Updated: 29/Mar/23 03:47
• Resolved: 29/Mar/23 03:47

Description

• When a key is deleted by a user, it is not immediately removed from the OM's metadata. Instead, the key is marked for deletion and moved to the DeletedTable, where it remains until it is permanently removed by the KeyDeletingService. The KeyDeletingService sends requests to the Storage Container Manager (SCM) to delete the corresponding data blocks associated with the keys. If the deletion is successful, the keys are removed from the OM's metadata.
• Once Recon detects the deletion, it updates its metadata store to reflect the change. This ensures that the deleted key is not included in any future searches or queries against the metadata store.
• Recon also retains a record of the deleted key in the DeletedTable in its own OM-metadata store. This allows administrators to query the metadata store for deleted keys and to see when they were deleted.
• This information can be useful for auditing, compliance, and troubleshooting purposes.

The Jira is coming out of the following discussion :- https://github.com/apache/ozone/pull/4266#issuecomment-1433096670

Issue Links

• links to: GitHub Pull Request #4406