openstack/swift
Code Issues Proposed changes
master
swift/doc/source/api/container_quotas.rst
Tim Burke cbba65ac91 quotas: Add account-level per-policy quotas 
Reseller admins can set new headers on accounts like

   X-Account-Quota-Bytes-Policy-<policy-name>: <quota>

This may be done to limit consumption of a faster, all-flash policy, for
example.

This is independent of the existing X-Account-Meta-Quota-Bytes header, which
continues to limit the total storage for an account across all policies.

Change-Id: Ib25c2f667e5b81301f8c67375644981a13487cfe
2023-03-21 17:27:31 +00:00

1.2 KiB
Raw Permalink Blame History

Container quotas

You can set quotas on the size and number of objects stored in a container by setting the following metadata:

  • X-Container-Meta-Quota-Bytes. The size, in bytes, of objects that can be stored in a container.
  • X-Container-Meta-Quota-Count. The number of objects that can be stored in a container.

When you exceed a container quota, subsequent requests to create objects fail with a 413 Request Entity Too Large error.

The Object Storage system uses an eventual consistency model. When you create a new object, the container size and object count might not be immediately updated. Consequently, you might be allowed to create objects even though you have actually exceeded the quota.

At some later time, the system updates the container size and object count to the actual values. At this time, subsequent requests fails. In addition, if you are currently under the X-Container-Meta-Quota-Bytes limit and a request uses chunked transfer encoding, the system cannot know if the request will exceed the quota so the system allows the request. However, once the quota is exceeded, any subsequent uploads that use chunked transfer encoding fail.