[HDDS-7479] Investigate -100% Volume and bucket quotas working

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Assignee: Sumit Agrawal
• Reporter: Sumit Agrawal
• Created: 11/Nov/22 12:22
• Updated: 26/Jun/23 08:50
• Resolved: 26/Jun/23 08:50

Description

Need verify quota feature and fix issues:

1. Volume and bucket relationship
2. Bucket with Legacy layout
3. Bucket with FSO layout
4. verify all FS feature for FSO layout related to quota
5. Review code for missing scenario

Issue Links

• is a parent of: HDDS-4257 support quota on key prefix
• is a parent of: HDDS-4565 [FSO]Delete : quotaReleased on directory deletion should consider all sub paths
• is a parent of: HDDS-4249 The usage value needs to be adjusted after client crash
• is a parent of: HDDS-4620 Should remove allocated quota when open key are cleaned up
• is a parent of: HDDS-7346 Cannot set bucket args when the volume has quota set
• is a parent of: HDDS-7598 Quota for snapshot handling
• is a parent of: HDDS-7152 usedBytes and usedNamespace not updated for FSO buckets
• is a parent of: HDDS-4129 Change MAX_QUOTA_IN_BYTES to Long.MAX_VALUE
• is duplicated by: HDDS-7497 Ozone fs `mkdir` does not update bucket's `usedNamespace`
• is related to: HDDS-4273 Volume Namespace:`usedNamespace` works by `ozone sh vol info`
• is related to: HDDS-6650 S3MultipartUpload support update bucket usedNamespace.
• is related to: HDDS-8630 Trash operation doesn't work as expected with Namespace quota set
• is related to: HDDS-8646 [Quota] Ozone key put fails during parallel writes with space quota set