[
https://issues.apache.org/jira/browse/HDDS-11437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881242#comment-17881242
]
Sumit Agrawal commented on HDDS-11437:
--------------------------------------
There is a change in behavior from client {*}1.0.0 to 1.1.0{*}. If quota is not
provided while create volume, it assumes to be having MAX_QUOTA_IN_BYTES
(Long.MAX_VALUE), but later its changed.
The restriction is put via HDDS-7751 to handle inconsistency and performance
in verifying volume quota wrt all bucket quota usages.
Proper support of quota is provided from 1.4.0 version. For above case, we can
use below command to remove quota.
ozone sh volume clrquota
!image-2024-09-12-14-34-45-897.png|width=916,height=241!
[~adoroszlai] IMO, this is not required to be handled for compatibility for
quota for 1.0.0 client and workaround to handle same is available to correct
quota set.
> Wire incompatibility in volume quota from 1.0.0
> -----------------------------------------------
>
> Key: HDDS-11437
> URL: https://issues.apache.org/jira/browse/HDDS-11437
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Client, Ozone Manager
> Reporter: Attila Doroszlai
> Assignee: Sumit Agrawal
> Priority: Major
> Attachments: image-2024-09-12-14-34-45-897.png
>
>
> Volume created without quota by Ozone 1.0.0 client in Ozone 1.5.0 cluster has
> non-zero quota. Bucket creation fails due to missing quota. In addition,
> response uses error code unknown to 1.0.0 client.
> {code:title=Ozone 1.0.0 client}
> $ ozone sh volume create /vol1
> $ ozone sh volume info /vol1 | jq -r '.quota'
> 1152921504606846976
> $ time ozone sh bucket create /vol1/bucket1
> Message missing required fields: status
> real 4m0.978s
> {code}
> {code:title=OM}
> [om1-OMStateMachineApplyTransactionThread - 0] ERROR
> bucket.OMBucketCreateRequest: Bucket creation failed for bucket:bucket1 in
> volume:vol1
> QUOTA_ERROR org.apache.hadoop.ozone.om.exceptions.OMException: Bucket space
> quota in this volume should be set as volume space quota is already set.
> at
> org.apache.hadoop.ozone.om.request.bucket.OMBucketCreateRequest.checkQuotaBytesValid(OMBucketCreateRequest.java:366)
> at
> org.apache.hadoop.ozone.om.request.bucket.OMBucketCreateRequest.validateAndUpdateCache(OMBucketCreateRequest.java:239)
> at
> org.apache.hadoop.ozone.protocolPB.OzoneManagerRequestHandler.lambda$0(OzoneManagerRequestHandler.java:419)
> at
> org.apache.hadoop.ozone.util.MetricUtil.captureLatencyNs(MetricUtil.java:46)
> at
> org.apache.hadoop.ozone.protocolPB.OzoneManagerRequestHandler.handleWriteRequestImpl(OzoneManagerRequestHandler.java:417)
> at
> org.apache.hadoop.ozone.protocolPB.RequestHandler.handleWriteRequest(RequestHandler.java:63)
> at
> org.apache.hadoop.ozone.om.ratis.OzoneManagerStateMachine.runCommand(OzoneManagerStateMachine.java:543)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
