Skip to main content

Change the consistency level

Contributors netapp-lhalbert netapp-perveilerk
PDFs

If you are using an S3 tenant, you can use the Tenant Manager or the Tenant Management API to change the consistency control for operations performed on the objects in S3 buckets.

What you'll need

  • You must be signed in to the Tenant Manager using a supported web browser.

  • You must belong to a user group that has the Manage All Buckets or the Root Access permission. These permissions override the permissions settings in group or bucket policies. See Tenant management permissions.

About this task

Consistency level provides 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 STORAGE (S3) > Buckets.

  2. Select the bucket name from the list.

    The bucket details page appears.

  3. Select Bucket options > Consistency level.

  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 do not exist). Not supported for S3 FabricPool buckets.

  5. Select Save changes.