GET container consistency request
Suggest changes
PDFs
Consistency controls provide a balance between the availability of the objects and the consistency of those objects across different Storage Nodes and sites. The GET container consistency request allows you to determine the consistency level being applied to a particular container.
Request
| Request HTTP Header | Description |
|---|---|
|
Specifies the Swift authentication token for the account to use for the request. |
|
Specifies the type of request, where |
|
The hostname to which the request is directed. |
Request example
GET /v1/28544923908243208806/Swift container X-Auth-Token: SGRD_3a877009a2d24cb1801587bfa9050f29 x-ntap-sg-consistency: true Host: test.com
Response
| Response HTTP Header | Description |
|---|---|
|
The date and time of the response. |
|
Whether the connection to the server is open or closed. |
|
The unique transaction identifier for the request. |
|
The length of the response body. |
|
The consistency control level being applied to the container. The following values are supported: all: 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. Recommended for most cases. available: Provides eventual consistency for both new objects and object updates. For S3 buckets, use only as required (for example, for a bucket that contains log values that are rarely read, or for HEAD or GET operations on keys that don't exist). Not supported for S3 FabricPool buckets. |
Response example
HTTP/1.1 204 No Content Date: Sat, 29 Nov 2015 01:02:18 GMT Connection: CLOSE X-Trans-Id: 1936575373 Content-Length: 0 x-ntap-sg-consistency: strong-site