This page explains which Cloud Storage operations are strongly consistent and which are eventually consistent. In the case of cacheable, publicly readable objects, you control the degree to which operations on the objects are consistent.
Strongly consistent operations
Cloud Storage provides strong global consistency for the following operations, including both data and metadata:
- Bucket listing
- Object listing
When you upload an object to Cloud Storage, and you receive a success
response, the object is immediately available for download and metadata
operations from any location where Google offers service. This is true whether
you create a new object or overwrite an existing object. Because uploads are
strongly consistent, you will never receive a
404 Not Found response or stale
data for a read-after-write or read-after-metadata-update operation.
In addition, when an upload request succeeds, it means your data is replicated in multiple data centers. The latency for writing to Cloud Storage's globally consistent, replicated store might be slightly higher than for a non-replicated or non-committed store. This is because a success response is returned only when multiple writes complete, not just one.
Strong global consistency also extends to deletion operations on objects. If a
deletion request succeeds, an immediate attempt to download the object or its
metadata will result in a
404 Not Found status code. You get the
because the object no longer exists after the delete operation succeeds.
Bucket listing and object listing are strongly consistent: when you create a
bucket or object and then immediately perform the relevant
list operation, the
newly created bucket or object appears in the returned list.
For buckets, while metadata updates are strongly consistent for read-after-metadata-update operations, the resulting configuration changes may take time to propagate. For example, if you enable object versioning on a bucket, you should wait at least 30 seconds before deleting or overwriting objects.
Similarly for HMAC keys, there is a delay of up to 3 minutes between when you request to change the key state and when the state change takes effect. For example, if you disable an HMAC key, you should wait at least 3 minutes before making a request to delete the key, because attempts to do so in the first 3 minutes could fail.
Eventually consistent operations
The following operations are eventually consistent:
- Granting access to or revoking access from resources.
It typically takes about a minute for these operations to take effect. In some cases, it might take several minutes longer.
As an example of behavior that can arise from eventual consistency, if you remove a user's access to a bucket, this change is immediately reflected in the metadata for the bucket; however, the user may still have access to the bucket for a short period of time.
Cache control and consistency
Cached objects that are publicly readable might not exhibit strong consistency. If you allow an object to be cached, and the object is in the cache when it is updated or deleted, the cached object is not updated or deleted until its cache lifetime expires.
The cache lifetime of an object is defined by the
associated with the object. The
Cache-Control metadata can be set using a
Cache-Control request header included in the initial upload of the object,
or in a subsequent update to the metadata of the object. Because you
Cache-Control metadata, you also control the degree to which
cached objects are consistent. Moreover, while requests for
the object can include their own
Cache-Control header, these headers are
ignored by Cloud Storage if they're set to avoid cached content.