[
https://issues.apache.org/jira/browse/HDDS-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759449#comment-17759449
]
Sammi Chen commented on HDDS-9153:
----------------------------------
[~erose], the current behavior, that once a volume has quota set, it requires
all its buckets has quota set too, the motivation is performance. The check
requires hold the write lock, If it allows bucket without quota under a volume
with quota, then every block allocation requires not only holds the the bucket
lock, but also the volume lock. All buckets will compete the volume lock
during block allocation. So it's a result of trade off between performance and
functionality.
> Do not require quotas for all buckets in a volume with quota
> ------------------------------------------------------------
>
> Key: HDDS-9153
> URL: https://issues.apache.org/jira/browse/HDDS-9153
> Project: Apache Ozone
> Issue Type: Improvement
> Components: OM
> Affects Versions: 1.4.0
> Reporter: Ethan Rose
> Priority: Major
>
> Currently, if a volume has a quota specified, all buckets created under the
> volume must also have a quota specified. It would be easier for admins to
> manage if this restriction was removed, so that individual buckets in the
> volume did not need their quota set, but their total usage must remain within
> the volume quota.
> Functionally, this should be straightforward. We are already tracking bucket
> space usage for all buckets even if they do not have a quota set. All write
> requests are serialized (including quota updates), and all write requests
> already update the volume space usage as well. We would just need to check
> the updated volume usage against the volume quota if no bucket quota is set.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
