Unsolved
This post is more than 5 years old
40 Posts
0
1936
object propagation
I issue a PUT or POST followed by a GET of the some object. Is there any latency in the processing of the object update/creation such that a GET may retrieve and old copy of the object or get a Not Found error? S3 has such an issue with their distributed architecture. What is the Atmos behavior? If this behavior exists are there any best practices for minimizing the possability of this occuring such as sending all requests to the same server?
rbala1
222 Posts
0
November 16th, 2009 07:00
We also have a distributed architecture where synchronization needs to occur between various internal components.
For instance, it's possible that attempting to delete an object immediately after it's created could result in an error that the object doesn't exist. A similar condition could occur when adding or modifying object metadata.
There's no way to assure that your application sends requests to a particular component. If you application expect to see immediate changes we would encourage retry.
Raj