Skip to main content

Change a bucket's consistency level

Contributors netapp-madkat netapp-lhalbert netapp-perveilerk ssantho3
PDFs

If you are using an S3 tenant, you can change the consistency level for operations performed on the objects in S3 buckets.

Before you begin
About this task

Consistency controls provide a balance between the availability of the objects and the consistency of those objects across different Storage Nodes and sites. In general, you should use the Read-after-new-write consistency level for your buckets.

If the Read-after-new-write consistency level does not meet the client application's requirements, you can change the consistency level by setting the bucket consistency level or by using the Consistency-Control header. The Consistency-Control header overrides the bucket consistency level.

Note When you change a bucket's consistency level, only those objects that are ingested after the change are guaranteed to meet the revised level.
Steps

  1. Select View buckets from the dashboard, or select STORAGE (S3) > Buckets.

  2. Select the bucket name from the table.

    The bucket details page appears.

  3. From the Bucket options tab, select the Consistency level accordion.

  4. Select a consistency level for operations performed on the objects in this bucket.

    • All: Provides the highest level of 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. 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.

  5. Select Save changes.