You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Gargi-jais11 (via GitHub)" <gi...@apache.org> on 2026/01/22 09:10:33 UTC

[PR] HDDS-14460. [Website v2] [Docs] [Core Concepts] Volume Quotas [ozone-site]

Gargi-jais11 opened a new pull request, #275:
URL: https://github.com/apache/ozone-site/pull/275

   ## What changes were proposed in this pull request?
   
   Fill the v2 doc Core Concepts -> Namespace -> Volume -> Quotas.
   
   Do not migrate from v1 doc https://ozone.apache.org/docs/edge/feature/quota.html it is too convoluted. Instead, use the content from this PR: https://github.com/apache/ozone-site/pull/149/changes?file-filters%5B%5D=.md#diff-88b901de56faa800036dbf2001697d28b247bb437f5f17ed1c297df27d832cec
   
   ## What is the link to the Apache Jira?
   
   https://issues.apache.org/jira/browse/HDDS-14460
   
   ## How was this patch tested?
   
   Check off which of the following tests were done on this change. If additional testing was done, please elaborate here as well.
   
   - [ ] The CI checks on my fork are passing
   - [ ] I verified the rendered content using a local preview
   - [ ] I manually verified the steps provided in this change work as described
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org


Re: [PR] HDDS-14460. [Website v2] [Docs] [Core Concepts] Volume Quotas [ozone-site]

Posted by "jojochuang (via GitHub)" <gi...@apache.org>.
jojochuang commented on code in PR #275:
URL: https://github.com/apache/ozone-site/pull/275#discussion_r2719978308


##########
docs/03-core-concepts/03-namespace/01-volumes/03-quotas.md:
##########
@@ -4,4 +4,51 @@ sidebar_label: Quotas
 
 # Volume Quotas
 
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What are Volume Quotas?
+
+Volume quotas in Ozone provide a mechanism to limit resource consumption at the volume level. They enable administrators to control and manage storage resources in multi-tenant environments, preventing any single volume from monopolizing cluster resources.
+
+Quotas act as upper bounds that constrain how much storage space and how many objects can be stored within a volume. When quotas are set, Ozone enforces these limits during write operations, ensuring that resource usage stays within the defined boundaries.
+
+## Quota Management
+
+Ozone defines two types of quota: namespace quota and storage space quota.
+
+- **Namespace Quota:** A namespace quota limits the number of objects in a volume. This number cannot be greater than `LONG.MAX_VALUE` in Java.
+- **Storage Space Quota:** A storage space quota limits the maximum used space of a volume. It allows the use of units B, KB, MB, GB and TB.
+
+### Key Characteristics
+
+- **Hierarchical Enforcement:** Volume quotas apply to the aggregate of all contained buckets
+- **Visibility:** Quota usage and limits can be monitored through the CLI and management interfaces
+- **Enforcement:** When a quota is reached, write operations fail with a descriptive error message
+
+:::note Important Notes
+
+- By default, the volume quota is unlimited.
+- The total quota of the buckets cannot exceed the volume quota.
+- Volume quota has no effect if bucket quota is not set.
+- 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.
+- 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 the volume or bucket is old) is not recommended. Since the old key is not counted to the bucket's usedBytes and namespace quota, the quota setting is inaccurate at this point.
+
+:::
+
+## Setting Both Quotas Simultaneously
+
+You can set both space and namespace quotas at the same time:
+
+```bash
+# Set both space (1TB) and namespace (1 million objects) quotas simultaneously
+ozone sh volume setquota --space=1TB --count=1000000 /volume1

Review Comment:
   ```suggestion
   ozone sh volume setquota --space-quota=1TB --namespace-quota=1000000 /volume1
   ```



##########
docs/03-core-concepts/03-namespace/01-volumes/03-quotas.md:
##########
@@ -4,4 +4,51 @@ sidebar_label: Quotas
 
 # Volume Quotas
 
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What are Volume Quotas?
+
+Volume quotas in Ozone provide a mechanism to limit resource consumption at the volume level. They enable administrators to control and manage storage resources in multi-tenant environments, preventing any single volume from monopolizing cluster resources.
+
+Quotas act as upper bounds that constrain how much storage space and how many objects can be stored within a volume. When quotas are set, Ozone enforces these limits during write operations, ensuring that resource usage stays within the defined boundaries.
+
+## Quota Management
+
+Ozone defines two types of quota: namespace quota and storage space quota.
+
+- **Namespace Quota:** A namespace quota limits the number of objects in a volume. This number cannot be greater than `LONG.MAX_VALUE` in Java.
+- **Storage Space Quota:** A storage space quota limits the maximum used space of a volume. It allows the use of units B, KB, MB, GB and TB.
+
+### Key Characteristics
+
+- **Hierarchical Enforcement:** Volume quotas apply to the aggregate of all contained buckets
+- **Visibility:** Quota usage and limits can be monitored through the CLI and management interfaces
+- **Enforcement:** When a quota is reached, write operations fail with a descriptive error message
+
+:::note Important Notes
+
+- By default, the volume quota is unlimited.
+- The total quota of the buckets cannot exceed the volume quota.
+- Volume quota has no effect if bucket quota is not set.
+- 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.
+- 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 the volume or bucket is old) is not recommended. Since the old key is not counted to the bucket's usedBytes and namespace quota, the quota setting is inaccurate at this point.
+
+:::
+
+## Setting Both Quotas Simultaneously
+
+You can set both space and namespace quotas at the same time:
+
+```bash
+# Set both space (1TB) and namespace (1 million objects) quotas simultaneously
+ozone sh volume setquota --space=1TB --count=1000000 /volume1
+
+# Check current quota settings and usage
+ozone sh volume info /volume1
+
+# Clear the space quota (set space limit to unlimited)
+ozone sh volume clrquota --space /volume1

Review Comment:
   ```suggestion
   ozone sh volume clrquota --space-quota /volume1
   ```



##########
docs/03-core-concepts/03-namespace/01-volumes/03-quotas.md:
##########
@@ -4,4 +4,51 @@ sidebar_label: Quotas
 
 # Volume Quotas
 
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What are Volume Quotas?
+
+Volume quotas in Ozone provide a mechanism to limit resource consumption at the volume level. They enable administrators to control and manage storage resources in multi-tenant environments, preventing any single volume from monopolizing cluster resources.
+
+Quotas act as upper bounds that constrain how much storage space and how many objects can be stored within a volume. When quotas are set, Ozone enforces these limits during write operations, ensuring that resource usage stays within the defined boundaries.
+
+## Quota Management
+
+Ozone defines two types of quota: namespace quota and storage space quota.
+
+- **Namespace Quota:** A namespace quota limits the number of objects in a volume. This number cannot be greater than `LONG.MAX_VALUE` in Java.
+- **Storage Space Quota:** A storage space quota limits the maximum used space of a volume. It allows the use of units B, KB, MB, GB and TB.
+
+### Key Characteristics
+
+- **Hierarchical Enforcement:** Volume quotas apply to the aggregate of all contained buckets
+- **Visibility:** Quota usage and limits can be monitored through the CLI and management interfaces
+- **Enforcement:** When a quota is reached, write operations fail with a descriptive error message
+
+:::note Important Notes
+
+- By default, the volume quota is unlimited.
+- The total quota of the buckets cannot exceed the volume quota.
+- Volume quota has no effect if bucket quota is not set.
+- 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.
+- 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 the volume or bucket is old) is not recommended. Since the old key is not counted to the bucket's usedBytes and namespace quota, the quota setting is inaccurate at this point.
+
+:::
+
+## Setting Both Quotas Simultaneously
+
+You can set both space and namespace quotas at the same time:
+
+```bash
+# Set both space (1TB) and namespace (1 million objects) quotas simultaneously
+ozone sh volume setquota --space=1TB --count=1000000 /volume1
+
+# Check current quota settings and usage
+ozone sh volume info /volume1
+
+# Clear the space quota (set space limit to unlimited)
+ozone sh volume clrquota --space /volume1
+
+# Clear the namespace quota (set object count limit to unlimited)
+ozone sh volume clrquota --count /volume1

Review Comment:
   ```suggestion
   ozone sh volume clrquota --namespace-quota /volume1
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org


Re: [PR] HDDS-14460. [Website v2] [Docs] [Core Concepts] Volume Quotas [ozone-site]

Posted by "jojochuang (via GitHub)" <gi...@apache.org>.
jojochuang commented on code in PR #275:
URL: https://github.com/apache/ozone-site/pull/275#discussion_r2719109163


##########
docs/03-core-concepts/03-namespace/01-volumes/03-quotas.md:
##########
@@ -4,4 +4,76 @@ sidebar_label: Quotas
 
 # Volume Quotas
 
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What are Volume Quotas?
+
+Volume quotas in Ozone provide a mechanism to limit resource consumption at the volume level. They enable administrators to control and manage storage resources in multi-tenant environments, preventing any single volume from monopolizing cluster resources.
+
+Quotas act as upper bounds that constrain how much storage space and how many objects can be stored within a volume. When quotas are set, Ozone enforces these limits during write operations, ensuring that resource usage stays within the defined boundaries.
+
+## Quota Management
+
+Quotas provide a mechanism to control resource utilization at the volume level:
+
+- **Space Quotas:** Limit the total amount of storage (in bytes) a volume can use. It allows the use of units B, KB, MB, GB and TB.
+- **Namespace Quotas:** Limit the total number of objects that can be stored within a volume. This number cannot be greater than `LONG.MAX_VALUE` in Java.
+- **Hierarchical Enforcement:** Volume quotas apply to the aggregate of all contained buckets
+- **Visibility:** Quota usage and limits can be monitored through the CLI and management interfaces
+- **Enforcement:** When a quota is reached, write operations fail with a descriptive error message
+

Review Comment:
   We can add a few notes:
   
   1. By default, the volume quota is unlimited.
   2. the total quota of the buckets, cannot exceed the volume quota.
   3. Volume quota has no effect if bucket quota is not set.
   4. 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.



##########
docs/03-core-concepts/03-namespace/01-volumes/03-quotas.md:
##########
@@ -4,4 +4,76 @@ sidebar_label: Quotas
 
 # Volume Quotas
 
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What are Volume Quotas?
+
+Volume quotas in Ozone provide a mechanism to limit resource consumption at the volume level. They enable administrators to control and manage storage resources in multi-tenant environments, preventing any single volume from monopolizing cluster resources.
+
+Quotas act as upper bounds that constrain how much storage space and how many objects can be stored within a volume. When quotas are set, Ozone enforces these limits during write operations, ensuring that resource usage stays within the defined boundaries.
+
+## Quota Management

Review Comment:
   Ozone defines two types of quota: namespace quota and storage space quota.
   
   A namespace quota limits the number of objects in a volume.
   A storage space quota limits the maximum used space of a volume.



##########
docs/03-core-concepts/03-namespace/01-volumes/03-quotas.md:
##########
@@ -4,4 +4,76 @@ sidebar_label: Quotas
 
 # Volume Quotas
 
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What are Volume Quotas?
+
+Volume quotas in Ozone provide a mechanism to limit resource consumption at the volume level. They enable administrators to control and manage storage resources in multi-tenant environments, preventing any single volume from monopolizing cluster resources.
+
+Quotas act as upper bounds that constrain how much storage space and how many objects can be stored within a volume. When quotas are set, Ozone enforces these limits during write operations, ensuring that resource usage stays within the defined boundaries.
+
+## Quota Management
+
+Quotas provide a mechanism to control resource utilization at the volume level:
+
+- **Space Quotas:** Limit the total amount of storage (in bytes) a volume can use. It allows the use of units B, KB, MB, GB and TB.
+- **Namespace Quotas:** Limit the total number of objects that can be stored within a volume. This number cannot be greater than `LONG.MAX_VALUE` in Java.
+- **Hierarchical Enforcement:** Volume quotas apply to the aggregate of all contained buckets
+- **Visibility:** Quota usage and limits can be monitored through the CLI and management interfaces
+- **Enforcement:** When a quota is reached, write operations fail with a descriptive error message
+
+## Setting only Storage Space Quota
+
+```bash
+# Create Volume with Storage Space Quota - This means setting the storage space of Volume1 to 5MB
+ozone sh volume create --space-quota 5MB /volume1
+
+# Set Storage Space Quota - This behavior changes the quota of Volume1 to 10GB
+ozone sh volume setquota --space-quota 10GB /volume1
+
+# Clear Storage Space Quota - This clears the space quota for the volume, setting the space limit to unlimited
+ozone sh volume clrquota --space-quota /volume1
+
+# Check Storage Space Quota and Usage - We can get the quota value and usedBytes in the info of the volume
+ozone sh volume info /volume1
+```
+
+:::note Storage Space Quota Notes
+
+- Decimals are not supported while setting quota for volume. For example, 1.5 TB is not allowed.
+- Ensure that the minimum storage quota is default block size × replication factor. If you set the value lesser than the default block size × replication factor, while writing the data (key put) operation, an operation error is displayed.
+- Total bucket quota should not be greater than its Volume quota. If we have a 10MB Volume, the sum of the sizes of all buckets under this volume cannot exceed 10MB, otherwise the bucket set quota fails.
+
+:::
+
+## Setting only Namespace Quota
+
+```bash
+# Create Volume with Namespace Quota - This means setting the namespace quota of Volume1 to 100
+ozone sh volume create --namespace-quota 100 /volume1
+
+# Set Namespace Quota - This behavior changes the namespace quota of Volume1 to 1000
+ozone sh volume setquota --namespace-quota 1000 /volume1
+
+# Clear Namespace Quota - This clears the namespace quota for the volume, setting the object count limit to unlimited
+ozone sh volume clrquota --namespace-quota /volume1
+
+# Check Namespace Quota and Usage - We can get the quota value and usedNamespace in the info of the volume
+ozone sh volume info /volume1
+```
+
+## Setting Both Quotas Simultaneously
+
+You can set both space and namespace quotas at the same time:
+
+```bash
+# Set both space (1TB) and namespace (1 million objects) quotas simultaneously
+ozone sh volume setquota --space=1TB --count=1000000 /volume1
+
+# Check current quota settings and usage
+ozone sh volume info /volume1
+
+# Clear the space quota (set space limit to unlimited)
+ozone sh volume clrquota --space /volume1
+
+# Clear the namespace quota (set object count limit to unlimited)
+ozone sh volume clrquota --count /volume1
+```

Review Comment:
   Let's remove the command CLI examples, because it duplicates https://ozone-site-v2.staged.apache.org/docs/administrator-guide/operations/quota
   ```suggestion
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org


Re: [PR] HDDS-14460. [Website v2] [Docs] [Core Concepts] Volume Quotas [ozone-site]

Posted by "Gargi-jais11 (via GitHub)" <gi...@apache.org>.
Gargi-jais11 commented on PR #275:
URL: https://github.com/apache/ozone-site/pull/275#issuecomment-3788153269

   Thanks @jojochuang for the review will do updates sooner.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org


Re: [PR] HDDS-14460. [Website v2] [Docs] [Core Concepts] Volume Quotas [ozone-site]

Posted by "jojochuang (via GitHub)" <gi...@apache.org>.
jojochuang commented on code in PR #275:
URL: https://github.com/apache/ozone-site/pull/275#discussion_r2719111448


##########
docs/03-core-concepts/03-namespace/01-volumes/03-quotas.md:
##########
@@ -4,4 +4,76 @@ sidebar_label: Quotas
 
 # Volume Quotas
 
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What are Volume Quotas?
+
+Volume quotas in Ozone provide a mechanism to limit resource consumption at the volume level. They enable administrators to control and manage storage resources in multi-tenant environments, preventing any single volume from monopolizing cluster resources.
+
+Quotas act as upper bounds that constrain how much storage space and how many objects can be stored within a volume. When quotas are set, Ozone enforces these limits during write operations, ensuring that resource usage stays within the defined boundaries.
+
+## Quota Management
+
+Quotas provide a mechanism to control resource utilization at the volume level:
+
+- **Space Quotas:** Limit the total amount of storage (in bytes) a volume can use. It allows the use of units B, KB, MB, GB and TB.
+- **Namespace Quotas:** Limit the total number of objects that can be stored within a volume. This number cannot be greater than `LONG.MAX_VALUE` in Java.
+- **Hierarchical Enforcement:** Volume quotas apply to the aggregate of all contained buckets
+- **Visibility:** Quota usage and limits can be monitored through the CLI and management interfaces
+- **Enforcement:** When a quota is reached, write operations fail with a descriptive error message
+
+## Setting only Storage Space Quota
+
+```bash
+# Create Volume with Storage Space Quota - This means setting the storage space of Volume1 to 5MB
+ozone sh volume create --space-quota 5MB /volume1
+
+# Set Storage Space Quota - This behavior changes the quota of Volume1 to 10GB
+ozone sh volume setquota --space-quota 10GB /volume1
+
+# Clear Storage Space Quota - This clears the space quota for the volume, setting the space limit to unlimited
+ozone sh volume clrquota --space-quota /volume1
+
+# Check Storage Space Quota and Usage - We can get the quota value and usedBytes in the info of the volume
+ozone sh volume info /volume1
+```
+
+:::note Storage Space Quota Notes
+
+- Decimals are not supported while setting quota for volume. For example, 1.5 TB is not allowed.
+- Ensure that the minimum storage quota is default block size × replication factor. If you set the value lesser than the default block size × replication factor, while writing the data (key put) operation, an operation error is displayed.
+- Total bucket quota should not be greater than its Volume quota. If we have a 10MB Volume, the sum of the sizes of all buckets under this volume cannot exceed 10MB, otherwise the bucket set quota fails.
+
+:::
+
+## Setting only Namespace Quota
+
+```bash
+# Create Volume with Namespace Quota - This means setting the namespace quota of Volume1 to 100
+ozone sh volume create --namespace-quota 100 /volume1
+
+# Set Namespace Quota - This behavior changes the namespace quota of Volume1 to 1000
+ozone sh volume setquota --namespace-quota 1000 /volume1
+
+# Clear Namespace Quota - This clears the namespace quota for the volume, setting the object count limit to unlimited
+ozone sh volume clrquota --namespace-quota /volume1
+
+# Check Namespace Quota and Usage - We can get the quota value and usedNamespace in the info of the volume
+ozone sh volume info /volume1
+```
+
+## Setting Both Quotas Simultaneously
+
+You can set both space and namespace quotas at the same time:
+
+```bash
+# Set both space (1TB) and namespace (1 million objects) quotas simultaneously
+ozone sh volume setquota --space=1TB --count=1000000 /volume1
+
+# Check current quota settings and usage
+ozone sh volume info /volume1
+
+# Clear the space quota (set space limit to unlimited)
+ozone sh volume clrquota --space /volume1
+
+# Clear the namespace quota (set object count limit to unlimited)
+ozone sh volume clrquota --count /volume1
+```

Review Comment:
   Let's remove the command CLI examples, because it duplicates https://ozone-site-v2.staged.apache.org/docs/administrator-guide/operations/quota
   ```suggestion
   ```
   
   instead, add a link to docs/administrator-guide/operations/quota



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org


Re: [PR] HDDS-14460. [Website v2] [Docs] [Core Concepts] Volume Quotas [ozone-site]

Posted by "Gargi-jais11 (via GitHub)" <gi...@apache.org>.
Gargi-jais11 commented on code in PR #275:
URL: https://github.com/apache/ozone-site/pull/275#discussion_r2719779188


##########
docs/03-core-concepts/03-namespace/01-volumes/03-quotas.md:
##########
@@ -4,4 +4,76 @@ sidebar_label: Quotas
 
 # Volume Quotas
 
-**TODO:** File a subtask under [HDDS-9857](https://issues.apache.org/jira/browse/HDDS-9857) and complete this page or section.
+## What are Volume Quotas?
+
+Volume quotas in Ozone provide a mechanism to limit resource consumption at the volume level. They enable administrators to control and manage storage resources in multi-tenant environments, preventing any single volume from monopolizing cluster resources.
+
+Quotas act as upper bounds that constrain how much storage space and how many objects can be stored within a volume. When quotas are set, Ozone enforces these limits during write operations, ensuring that resource usage stays within the defined boundaries.
+
+## Quota Management
+
+Quotas provide a mechanism to control resource utilization at the volume level:
+
+- **Space Quotas:** Limit the total amount of storage (in bytes) a volume can use. It allows the use of units B, KB, MB, GB and TB.
+- **Namespace Quotas:** Limit the total number of objects that can be stored within a volume. This number cannot be greater than `LONG.MAX_VALUE` in Java.
+- **Hierarchical Enforcement:** Volume quotas apply to the aggregate of all contained buckets
+- **Visibility:** Quota usage and limits can be monitored through the CLI and management interfaces
+- **Enforcement:** When a quota is reached, write operations fail with a descriptive error message
+
+## Setting only Storage Space Quota
+
+```bash
+# Create Volume with Storage Space Quota - This means setting the storage space of Volume1 to 5MB
+ozone sh volume create --space-quota 5MB /volume1
+
+# Set Storage Space Quota - This behavior changes the quota of Volume1 to 10GB
+ozone sh volume setquota --space-quota 10GB /volume1
+
+# Clear Storage Space Quota - This clears the space quota for the volume, setting the space limit to unlimited
+ozone sh volume clrquota --space-quota /volume1
+
+# Check Storage Space Quota and Usage - We can get the quota value and usedBytes in the info of the volume
+ozone sh volume info /volume1
+```
+
+:::note Storage Space Quota Notes
+
+- Decimals are not supported while setting quota for volume. For example, 1.5 TB is not allowed.
+- Ensure that the minimum storage quota is default block size × replication factor. If you set the value lesser than the default block size × replication factor, while writing the data (key put) operation, an operation error is displayed.
+- Total bucket quota should not be greater than its Volume quota. If we have a 10MB Volume, the sum of the sizes of all buckets under this volume cannot exceed 10MB, otherwise the bucket set quota fails.
+
+:::
+
+## Setting only Namespace Quota
+
+```bash
+# Create Volume with Namespace Quota - This means setting the namespace quota of Volume1 to 100
+ozone sh volume create --namespace-quota 100 /volume1
+
+# Set Namespace Quota - This behavior changes the namespace quota of Volume1 to 1000
+ozone sh volume setquota --namespace-quota 1000 /volume1
+
+# Clear Namespace Quota - This clears the namespace quota for the volume, setting the object count limit to unlimited
+ozone sh volume clrquota --namespace-quota /volume1
+
+# Check Namespace Quota and Usage - We can get the quota value and usedNamespace in the info of the volume
+ozone sh volume info /volume1
+```
+
+## Setting Both Quotas Simultaneously
+
+You can set both space and namespace quotas at the same time:
+
+```bash
+# Set both space (1TB) and namespace (1 million objects) quotas simultaneously
+ozone sh volume setquota --space=1TB --count=1000000 /volume1
+
+# Check current quota settings and usage
+ozone sh volume info /volume1
+
+# Clear the space quota (set space limit to unlimited)
+ozone sh volume clrquota --space /volume1
+
+# Clear the namespace quota (set object count limit to unlimited)
+ozone sh volume clrquota --count /volume1
+```

Review Comment:
   I think we should keep `# Setting Both Quotas Simultaneously` this section as it is not mentioned in the quota documentations and cli commands are also separate



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org


Re: [PR] HDDS-14460. [Website v2] [Docs] [Core Concepts] Volume Quotas [ozone-site]

Posted by "jojochuang (via GitHub)" <gi...@apache.org>.
jojochuang merged PR #275:
URL: https://github.com/apache/ozone-site/pull/275


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org