Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Need verify quota feature and fix issues:
- Volume and bucket relationship
- Bucket with Legacy layout
- Bucket with FSO layout
- verify all FS feature for FSO layout related to quota
- Review code for missing scenario
Attachments
Issue Links
- is a parent of
-
HDDS-4257 support quota on key prefix
- Open
-
HDDS-4565 [FSO]Delete : quotaReleased on directory deletion should consider all sub paths
- Resolved
-
HDDS-4249 The usage value needs to be adjusted after client crash
- Resolved
-
HDDS-4620 Should remove allocated quota when open key are cleaned up
- Resolved
-
HDDS-7346 Cannot set bucket args when the volume has quota set
- Resolved
-
HDDS-7598 Quota for snapshot handling
- Resolved
-
HDDS-7152 usedBytes and usedNamespace not updated for FSO buckets
- Resolved
-
HDDS-4129 Change MAX_QUOTA_IN_BYTES to Long.MAX_VALUE
- Resolved
- is duplicated by
-
HDDS-7497 Ozone fs `mkdir` does not update bucket's `usedNamespace`
- Resolved
- is related to
-
HDDS-4273 Volume Namespace:`usedNamespace` works by `ozone sh vol info`
- Resolved
-
HDDS-6650 S3MultipartUpload support update bucket usedNamespace.
- Resolved
-
HDDS-8630 Trash operation doesn't work as expected with Namespace quota set
- Resolved
-
HDDS-8646 [Quota] Ozone key put fails during parallel writes with space quota set
- Resolved