GET Bucket consistency request

The GET Bucket consistency request allows you to determine the consistency level being applied to a particular bucket.

The default consistency controls are set to guarantee read-after-write for newly created objects.

You must have the s3:GetBucketConsistency permission, or be account root, to complete this operation.

Request example

GET /bucket?x-ntap-sg-consistency HTTP/1.1
Date: date
Authorization: authorization string
Host: host

Response

In the response XML, <Consistency> will return one of the following values:

Consistency control Description
all Provides the highest guarantee of read-after-write consistency. All nodes receive the data immediately, or the request will fail.
strong-global Guarantees read-after-write consistency for all client requests across all sites.
strong-site Guarantees read-after-write consistency for all client requests within a site.
read-after-new-write (Default) Provides read-after-write consistency for new objects and eventual consistency for object updates. Offers high availability and data protection guarantees. Matches AWS S3 consistency guarantees.
Note: If your application uses HEAD requests on objects that do not exist, you might receive a high number of 500 Internal Server errors if one or more Storage Nodes are unavailable. To prevent these errors, set the consistency control to "available" unless you require consistency guarantees similar to AWS S3.
available (eventual consistency for HEAD operations) Behaves the same as the "read-after-new-write" consistency level, but only provides eventual consistency for HEAD operations. Offers higher availability for HEAD operations than "read-after-new-write" if Storage Nodes are unavailable. Differs from AWS S3 consistency guarantees for HEAD operations only.
weak Provides eventual consistency and high availability, with minimal data protection guarantees, especially if a Storage Node fails or is unavailable. Suitable only for write-heavy workloads that require high availability, do not require read-after-write consistency, and can tolerate the potential loss of data if a node fails.

Response example

HTTP/1.1 200 OK
Date: Sat, 29 Nov 2015 01:02:18 GMT
Connection: CLOSE
Server: StorageGRID/10.3.0
x-amz-request-id: 12345
Content-Length: 127
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>
<Consistency xmlns="http://s3.storagegrid.com/doc/2015-02-01/">default</Consistency>