6f9ca6122e
After discussion https://review.openstack.org/#/c/129384/ moving to the doc directory in swift repo. This lets us eliminate the object-api repo along with all the <service>- api repos and move content to audience-centric locations. Change-Id: Ia0d9973847f7409a02dcc1a0e19400a3c3ecdf32
31 lines
1.2 KiB
ReStructuredText
31 lines
1.2 KiB
ReStructuredText
================
|
|
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.
|
|
|