[
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.
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!
was:
long quotaInBytes and long quotaInCounts 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.
Currently we provide clrQuota mode to set it to -1 (no enable quota). We cannot
change all quotas from 0 to -1 at one time automatic, since it is possible that
the user himself would actively set the quota to 0.
So when this happens we need to prompt the user, they can use clrQuota to set
it to -1.
!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.
> 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!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
