An ingest, or save, operation consists of a defined data flow between the client and the StorageGRID system. The system uses attributes to track the ingestion of the object and the available storage space.
Data flow
When a client saves an object to the StorageGRID system, the Storage Node processes the request and stores the metadata and data to disk.
- The client application creates the object and sends it to the StorageGRID system through an HTTP PUT request.
- The LDR service saves the object data as a replicated copy to disk.
- The LDR service sends the object metadata to a DDS service.
- The DDS service saves the object metadata to disk.
- The DDS service propagates copies of object metadata to other DDS services via the metadata store. These copies are also saved to disk.
- The LDR service returns an HTTP 200 OK response to the client to acknowledge that the object has been ingested.
- The object is then evaluated against the system's ILM policy.
Ingest related attributes
The table shows the primary attributes used to track the ingest of an object to the StorageGRID system:
| Component | Attribute changes |
|---|---|
| Object Data: The amount of replicated object data stored on the object store increases by an amount roughly equivalent to the newly ingested object's size. Object data may be initially stored as two replicated copies from dual commit, resulting in twice the space used. | |
| Total Objects: The total number of S3 and Swift data objects known by this grid node increases by one. |