[
https://issues.apache.org/jira/browse/HDDS-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mingchao zhao updated HDDS-4562:
--------------------------------
Description:
long quotaInBytes are new fields in the bucketArgs, this field will go to 0 by
default in the old bucket when the old cluster is upgraded. At this point, the
data writes are rejected because quota is 0.
This is similar to creating a bucket without specifying quotaInBytes, where
quotaInBytes is set to -1 by default via getQuotaValue. We can use 0 as a
special term.
!screenshot-quota.png!
was:
long quotaInBytes are new fields in the bucketArgs, this field will go to 0 by
default in the old bucket when the old cluster is upgraded. At this point, the
data writes are rejected because quota is 0.
When creating a bucket, quotaInBytes is not specified. In this case,
quotaInBytes will be set to -1 by default via getQuotaValue. We can use 0 as a
special term.
!screenshot-quota.png!
> Old bucket needs to be accessible after the cluster was upgraded to the Quota
> version.
> --------------------------------------------------------------------------------------
>
> Key: HDDS-4562
> URL: https://issues.apache.org/jira/browse/HDDS-4562
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: mingchao zhao
> Priority: Major
> Attachments: screenshot-quota.png
>
>
> long quotaInBytes are new fields in the bucketArgs, this field will go to 0
> by default in the old bucket when the old cluster is upgraded. At this point,
> the data writes are rejected because quota is 0.
> This is similar to creating a bucket without specifying quotaInBytes, where
> quotaInBytes is set to -1 by default via getQuotaValue. We can use 0 as a
> special term.
> !screenshot-quota.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
