A client application can send a delete request to the StorageGRID Webscale system at any time. This results in a removal of the object from the system.
Data flow
When a client triggers a delete, all copies of an object are removed
from the system.
- The LDR service receives a delete command from the client application.
- The LDR service forwards the delete request to the DDS service, which instructs the CMS service to remove all copies of object data.
- The object is removed from the system and is no longer known by the client.
Delete related attributes
The table shows the primary attributes used to track the deletion of an object from the StorageGRID Webscale system:
| Component | Attribute changes |
|---|---|
| Operations - Successful (SSUC): The total number of successful S3 operations increases by one. | |
| Operations - Successful (WSUC): The total number of successful Swift operations increases by one. | |
ILM Evaluations (ILev): Because an ILM evaluation is triggered each time a content handle is released, the total number of ILM evaluations increases when an object is deleted. Purges (DCpT): The number of object copies deleted increases by one on the CMS service for each copy of the object deleted from the LDR and ARC services. |
|
Total Objects (DATC): The total number of data objects in the StorageGRID Webscale system that are known by this DDS service decreases by one. S3 and Swift Objects (SDOC): When a data object is deleted by a client application that interfaces to the StorageGRID Webscale system through the S3 or Swift REST API, the total number of data objects known by this DDS service decreases by one. |