3 ms·
Because AWS gets to choose when the actual deletes happen. The metadata is marked as object deleted but AWS can process the delete off peak. It also avoids the
by bushbaba 2y ago
Because AWS gets to choose when the actual deletes happen. The metadata is marked as object deleted but AWS can process the delete off peak. It also avoids the s3 api server being hammered with qps
- yencabulator 2y agoAn explicit delete operation can mark metadata the same way. The real difference is likely more along the lines of LSM compaction, with expiry they likely use a moral equivalent of https://github.com/facebook/rocksdb/wiki/Compaction-Filter https://github.com/facebook/rocksdb/wiki/Compaction-Filter to actually do the deletion.
- bushbaba 2y agoThat’s called a delete marker in s3. Less IO than a true delete but also still can lead to high qps to s3 api server. https://docs.aws.amazon.com/AmazonS3/latest/userguide/DeleteMarker.html https://docs.aws.amazon.com/AmazonS3/latest/userguide/Delete...