[jira] [Created] (HDDS-15027) [Docs] [System Internals] Implementation of Delete Operations

["Wei-Chiu Chuang (Jira)" <ji...@apache.org>]

Wei-Chiu Chuang created HDDS-15027:
--------------------------------------

             Summary: [Docs] [System Internals] Implementation of Delete Operations
                 Key: HDDS-15027
                 URL: https://issues.apache.org/jira/browse/HDDS-15027
             Project: Apache Ozone
          Issue Type: Sub-task
          Components: documentation
            Reporter: Wei-Chiu Chuang


A very common question users ask is: when a user issues a delete request, how does it eventually get deleted? Due to Ozone's distributed nature, it can be tricky to understand all the moving parts, so this page gives a holistic overview of delete.

Trace every part of a delete request from beginning to end. This includes:

- Client getting encryption keys
- Client calling OM to delete the key
- OM validating client's Kerberos principal
- OM checking permissions (Ranger or Native ACLs) - OMKeyDeleteRequest
- OM marking the key for deletion and removing it from the namespace 
- OM acking to the client
- OM sending blocks to delete to SCM
- SCM sending blocks to delete to the Datanode
- Datanode removes data

Note that delete works the same regardless of replication type. Also document timing of background services and their batch size to estimate the rate of deletion.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org