bharatviswa504 commented on pull request #1677: URL: https://github.com/apache/ozone/pull/1677#issuecomment-744772894
> https://ci-hadoop.apache.org/view/Hadoop%20Ozone/job/ozone-doc-master/lastSuccessfulBuild/artifact/hadoop-hdds/docs/public/feature/quota.html 1. When clear volume quota(Assuming volume quota was set before), it is just like setting the quota on the volume to -1, when clear volume quota is called? 2. When volume quota is set, bucket clear quota, it is like just setting the quota for that bucket to -1, and it will allow new buckets can be created if volume quota is still available(As previous bucket quota cleared quota) When volume quota is not set and bucket quota is set, it is just reset quota of the bucket to -1. when clear bucket quota operation is performed Is my understanding correct here? Example: V1 - 100 MB V1/B1 - 50MB V1/B2- 50MB Now clear quota on V1/B2 we set quota of V1/B2 to -1, and now a new bucket can be still created in this volume? New Bucket created with quota 50MB. (V1/B3) So, in this volume there are 3 buckets, only 2 are considered in to count, as clearQuota is run(on V1/B2), and we are not considering this bucket in quota calculations, so this bucket will not be counted under quota, but for volume we have crossed the quota of that volume. (As user has run clear quota on V1/B2) So, here clear quota means resetting the quota to -1? Or what is the real purpose of this clearQuota usage on clusters, in what scenarios this will be useful on the cluster? >For old buckets, we do not recommend that quota be enabled, but in order not to affect the write, I handle the default at >checkBucketQuotaInBytes in this PR. But I don't see any guards in the cluster to not allow this for older buckets. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
