Delete data flow

All object copies are removed from the StorageGRID system when a client performs a delete operation or when the object's lifetime expires, triggering its automatic removal. There is a defined data flow for object deletion.

Client deletion

When a client deletes an object, all copies of the object are removed from the StorageGRID system.


Client delete data flow

  1. The LDR service receives a delete request from the client application.
  2. The LDR service updates the metadata store so the object looks deleted to client requests, and instructs the ILM engine to remove all copies of object data.
  3. The object is removed from the system. The metadata store is updated to remove object metadata.

Automatic object deletion

StorageGRID automatically deletes all copies of an object if one of the following conditions are met:

  • The object is in a compliant S3 bucket and the retention period ends (assumes automatic deletion is selected and the bucket is not under a legal hold).
  • The object is in an S3 bucket that has a lifecycle configuration, and the expiration date or number of days is met.
  • The last time period in the ILM rule ends and there are no further placements specified for the object (assumes the object is not in a compliant bucket).
Note: The Expiration action in an S3 bucket lifecycle always overrides ILM settings. As a result, an object might be retained on the grid even after any ILM instructions for placing the object have lapsed.
Automatic deletion data flow
  1. The ILM engine determines that the object needs to be deleted.
  2. The ILM engine notifies the metadata store. The metadata store updates object metadata so that the object looks deleted to client requests.
  3. The ILM engine removes all copies of the object. The metadata store is updated to remove object metadata.