StorageGRID protects objects during ingest either by performing synchronous placement or by performing dual commit, as specified in the ILM rule that matches the objects.
ingest successfulmessage to the client when all copies are created.
If StorageGRID cannot immediately create all object copies (for example, because a required location is temporarily unavailable), it either sends an ingest failed
message to the client, or it falls back to creating interim object copies and evaluating ILM later, depending on the choice you made when you created the ILM rule.
ingest successfulmessage to the client. StorageGRID then queues the object for ILM evaluation.
When StorageGRID performs the ILM evaluation, it first checks to see if the interim copies satisfy the placement instructions in the ILM rule. For example, the two interim copies might satisfy the instructions in a two-copy ILM rule, but they would not satisfy the instructions in an erasure-coding rule. If the interim copies do not satisfy the ILM instructions, StorageGRID creates new object copies and deletes any interim copies that are not needed.
By default, StorageGRID uses synchronous placement to protect objects during ingest.