Skip to content

HDDS-8016. updated the ozone doc for linked bucket and deletion async limitation #4526

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ChenSammi merged 4 commits into from
Apr 6, 2023
Merged

HDDS-8016. updated the ozone doc for linked bucket and deletion async limitation #4526

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
102efce
HDDS-8016. updated the ozone doc for linked bucket and deletion async…
sumitagrawl Apr 3, 2023
715d111
HDDS-8016. updated the ozone doc for linked bucket and deletion async…
sumitagrawl Apr 4, 2023
200265e
HDDS-8016. updated the ozone doc for linked bucket and deletion async…
sumitagrawl Apr 4, 2023
e63a3c0
Update Quota.zh.md
ChenSammi Apr 6, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions hadoop-hdds/docs/content/feature/Quota.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,8 @@ e. If the cluster is upgraded from old version less than 1.1.0, use of quota on

f. If volume's quota is enabled then bucket's quota cannot be cleared.

g. Volume having linked bucket do not consume space quota for keys within linked bucket. Linked bucket keys will consume space quota of source volume and source bucket.

2. Namespace quota

Administrators should be able to define how many namespace a Volume or Bucket can use. The following settings for namespace quota are supported:
Expand All @@ -55,9 +57,14 @@ b. When volume namespace quota is enabled, the total number of buckets under the

c. When bucket namespace quota is enabled, the total number of keys under the bucket, cannot exceed the bucket namespace quota.

d. Linked buckets do not consume namespace quota.
d. Linked buckets do not define separate namespace quota, it is referred by namespace quota of source bucket for keys inside linked bucket.

e. Linked bucket will consume namespace quota of volume.

f. If the cluster is upgraded from old version less than 1.1.0, use of quota on older volumes and buckets(We can confirm by looking at the info for the volume or bucket, and if the quota value is -2 then volume or bucket is old) is not recommended. Since the old key is not counted to the bucket's namespace quota, the quota setting is inaccurate at this point.

e. If the cluster is upgraded from old version less than 1.1.0, use of quota on older volumes and buckets(We can confirm by looking at the info for the volume or bucket, and if the quota value is -2 then volume or bucket is old) is not recommended. Since the old key is not counted to the bucket's namespace quota, the quota setting is inaccurate at this point.
### Note:
- For FSO bucket with recursive deletion of directory, release of quota happens asynchronously after sub directories and files are removed (when directory is removed, recursive deletion can be in-progress in background).

## Client usage
### Storage Space level quota
Expand Down
11 changes: 9 additions & 2 deletions hadoop-hdds/docs/content/feature/Quota.zh.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,8 @@ menu:

f. 如果volume quota被启用，那么bucket quota将不能被清除。

g. Volume内的linked bucket不消耗Volume的空间配额。linked bcuket将消耗源Volume和源Bucket的空间配额。

Copy link
Contributor

@ChenSammi ChenSammi Apr 4, 2023 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

g. Volume内的linked bucket不消耗Volume的空间配额。linked bcuket将消耗源Volume和源Bucket的空间配额。

Copy link
Contributor Author

@sumitagrawl sumitagrawl Apr 4, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated...

2. 命名空间配额

管理员应当能够定义一个Volume或Bucket可以使用多少命名空间。目前支持命名空间的配额设置为：
Expand All @@ -53,9 +55,14 @@ menu:

c. 当bucket的命名空间配额启用时，该bucket的key数目不能超过此配额。

d. Linked bucket不消耗命名空间配额。
d. Linked bucket 上不支持定义单独的命名空间配额，它直接引用源bucket的命名空间配额。

e. Linked bucket将消耗卷的命名空间配额。

f. 如果集群从小于1.1.0的旧版本升级而来，则不建议在旧volume和bucket(可以通过查看volume或者bucket的info确认，如果quota值是-2，那么这个volume或者bucket就是旧的)上使用配额。由于旧的key没有计算到bucket的命名空间配额中，所以此时配额设置是不准确的。

e. 如果集群从小于1.1.0的旧版本升级而来，则不建议在旧volume和bucket(可以通过查看volume或者bucket的info确认，如果quota值是-2，那么这个volume或者bucket就是旧的)上使用配额。由于旧的key没有计算到bucket的命名空间配额中，所以此时配额设置是不准确的。
### 笔记
- 对于FSO bucket，当递归删除目录时，配额将在子目录和文件被异步删除后释放（当目录被删除时，递归删除在后台进行）。

## 客户端用法
### Storage space级别配额
Expand Down