[
https://issues.apache.org/jira/browse/HDDS-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arafat Khan updated HDDS-7994:
---------------------------------------
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
was:
* 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.
> Expose information on keys marked for deletion and moved to the DeletedTable
> ----------------------------------------------------------------------------
>
> Key: HDDS-7994
> URL: https://issues.apache.org/jira/browse/HDDS-7994
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Recon
> Reporter: Mohammad Arafat Khan
> Assignee: Mohammad Arafat Khan
> Priority: Major
>
> * 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
