2 ms·
The same guarantees also apply to OpenStack Swift, which is basically S3-on-your-own-cloud. Since more and more internal teams are now using the Swift clusters
by majewsky 10y ago
The same guarantees also apply to OpenStack Swift, which is basically S3-on-your-own-cloud. Since more and more internal teams are now using the Swift clusters that I administer at $work, I can see a lot of people struggling with the concept of temporary inconsistency and the practical ramifications thereof.
Last year, I spent two full months hunting temporary inconsistency bugs in the Docker Registry's Swift driver. I added several heuristics that reduced the frequency of inconsistency-induced errors by about two orders of magnitude, but in the end, we still ended up switching to Quay, which has gotten the memo that you mentioned: "never overwrite anything, and never rely on object listing". They put metadata in an RDBMS instead, just like s3mper which was mentioned in the submission.