You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2020/10/14 12:13:00 UTC

[jira] [Resolved] (HDDS-4331) Space Quota: bucket quota not exceeded, volume needn’t check.

     [ https://issues.apache.org/jira/browse/HDDS-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mingchao zhao resolved HDDS-4331.
---------------------------------
    Resolution: Auto Closed

A bucket quota should not be greater than its Volume quota. Let's look at an example. If we have a 10MB Volume and create five buckets under that Volume with a quota of 5MB, the total quota is 25MB. In this case, the bucket creation will always succeed, and we check the quota for bucket and volume when the data is actually written. Each write needs to check whether the current bucket is exceeding the limit and the current total volume usage is exceeding the limit.
Bucket quota may not be exceeded when writing data, but volume quota may be. Therefore, volume quota still needs to be checked.


> Space Quota: bucket quota not exceeded, volume needn’t check.
> -------------------------------------------------------------
>
>                 Key: HDDS-4331
>                 URL: https://issues.apache.org/jira/browse/HDDS-4331
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: mingchao zhao
>            Assignee: mingchao zhao
>            Priority: Minor
>
> The quota check has an optimization point. If bucket sets quota and quota is not exceeded, then the volume's quota needn't checked and is definitely not exceeded.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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