From 7d848cbc7d83e1d484e6ecc19b6cb353f15ad955 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Sun, 23 Jan 2022 17:48:47 -0800 Subject: [PATCH] Updated S3 Bucket Quota (markdown) --- S3-Bucket-Quota.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/S3-Bucket-Quota.md b/S3-Bucket-Quota.md index 5897b29..909cf39 100644 --- a/S3-Bucket-Quota.md +++ b/S3-Bucket-Quota.md @@ -8,7 +8,7 @@ Since SeaweedFS uses one collection for each bucket, the usage can be efficientl There are two aspects of quota management: "quota configuration" and "quota enforcement". -* "Quota Configuration" is done in by an admin script in `weed shell`, where you can set/remove/enable/disable bucket quota. +* "Quota Configuration" is done in by an admin script in `weed shell`, where you can set/remove/enable/disable bucket quota for each bucket. * "Quota Enforcement" is actually also an admin script, which you can run it periodically by adding it to `master.toml`. It will check whether all the buckets are over their limit or not. If one bucket is over quota, it will set the bucket to read only. The bucket read only flag is checked when filer process write requests. If the bucket is read only, the creation and update requests on this bucket will be denied, except deletion. The read operations are not be affected.