5865c3b93d
Bucket quotas don't work the way people think they work, as they cannot enforce hard limits. Deprecate in docs while we sort out what to do with the commands. The future replacement is MinIO Enterprise Catalog. Staged: http://192.241.195.202:9000/staging/deprecate-bucket-quota/linux/reference/minio-mc-deprecated.html See: https://github.com/minio/mc/pull/5011 https://github.com/minio/mc/pull/5012
2.0 KiB
mc quota
minio
Table of Contents
mc quota
RELEASE.2024-07-31T15-58-33Z
mc quota and its subcommands are deprecated.
Description
The mc quota commands
configure, display, or remove a quota limit on a bucket.
When a bucket with a quota configured reaches the specified limit, as
determined by the MinIO object scanner, MinIO rejects further
PUT requests for the bucket.
Each time the MinIO object scanner <minio-lifecycle-management-scanner>
scans a bucket for pending object lifecycle transitions <minio-lifecycle-management>,
it also checks if the bucket has exceeded a configured quota.
Quota enforcement is not immediate
Bucket quotas are not intended to enforce a strict hard limit on a
bucket's size. If a bucket exceeds its quota between scanner passes,
MinIO continues to accept PUT requests for that bucket
until after_ the next scanner pass identifies
the quota violation.
Subcommands
mc quota includes the
following subcommands:
| Subcommand | Description |
|---|---|
~mc quota clear |
|
~mc quota info |
|
~mc quota set |
/reference/deprecated/mc-quota-clear /reference/deprecated/mc-quota-info /reference/deprecated/mc-quota-set