[ 
https://issues.apache.org/jira/browse/HDDS-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arun Sarin updated HDDS-8372:
-----------------------------
    Description: 
Minimum Storage quota should be default block size * replication factor

Currently while setting the storage quota, user is allowed to set the quota to 
values lesser than block size*replication factor .

Whereas while writing the data [key put] operation , the operation gets errored 
out because quota is being set to value lesser than default block size * 
replication factor

Should we restrict the setting of quota only to equal to or greater than 
default block size * replication factor or we can document  this in official 
documentation

Command Executed
{code:java}
[root@quasar-tvqwpy-1 /]# ozone sh key put /volume4/bucket4/key1 
/tmp/testdata/test
QUOTA_EXCEEDED The DiskSpace quota of bucket:bucket4 exceeded quotaInBytes: 
13500 Bytes but diskspace consumed: 805306368 Bytes.
[root@quasar-tvqwpy-1 /]# 
[root@quasar-tvqwpy-1 /]# 
[root@quasar-tvqwpy-1 /]# ozone sh bucket info /volume4/bucket4
{
  "metadata" : { },
  "volumeName" : "volume4",
  "name" : "bucket4",
  "storageType" : "DISK",
  "versioning" : false,
  "usedBytes" : 0,
  "usedNamespace" : 0,
  "creationTime" : "2023-04-04T07:07:28.246Z",
  "modificationTime" : "2023-04-04T07:38:41.902Z",
  "quotaInBytes" : 13500,
  "quotaInNamespace" : -1,
  "bucketLayout" : "LEGACY",
  "link" : false
}
[root@quasar-tvqwpy-1 /]# ls -lrt /tmp/testdata/
total 8
-rw-r--r-- 1 root root 4500 Apr  4 07:23 test {code}

  was:
Minimum Storage quota should be default block size * replication factor

Currently while setting the storage quota, user is allowed to set the quota to 
values lesser than block size*replication factor .

Whereas while writing the data [key put] operation , the operation gets errored 
out because quota is being set to value lesser than default block size * 
replication factor

Should we restrict the setting of quota only to equal to or greater than 
default block size * replication factor or we can document  this in official 
documentation


> Minimum Storage quota should be default block size * replication factor
> -----------------------------------------------------------------------
>
>                 Key: HDDS-8372
>                 URL: https://issues.apache.org/jira/browse/HDDS-8372
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Arun Sarin
>            Assignee: Arun Sarin
>            Priority: Minor
>
> Minimum Storage quota should be default block size * replication factor
> Currently while setting the storage quota, user is allowed to set the quota 
> to values lesser than block size*replication factor .
> Whereas while writing the data [key put] operation , the operation gets 
> errored out because quota is being set to value lesser than default block 
> size * replication factor
> Should we restrict the setting of quota only to equal to or greater than 
> default block size * replication factor or we can document  this in official 
> documentation
> Command Executed
> {code:java}
> [root@quasar-tvqwpy-1 /]# ozone sh key put /volume4/bucket4/key1 
> /tmp/testdata/test
> QUOTA_EXCEEDED The DiskSpace quota of bucket:bucket4 exceeded quotaInBytes: 
> 13500 Bytes but diskspace consumed: 805306368 Bytes.
> [root@quasar-tvqwpy-1 /]# 
> [root@quasar-tvqwpy-1 /]# 
> [root@quasar-tvqwpy-1 /]# ozone sh bucket info /volume4/bucket4
> {
>   "metadata" : { },
>   "volumeName" : "volume4",
>   "name" : "bucket4",
>   "storageType" : "DISK",
>   "versioning" : false,
>   "usedBytes" : 0,
>   "usedNamespace" : 0,
>   "creationTime" : "2023-04-04T07:07:28.246Z",
>   "modificationTime" : "2023-04-04T07:38:41.902Z",
>   "quotaInBytes" : 13500,
>   "quotaInNamespace" : -1,
>   "bucketLayout" : "LEGACY",
>   "link" : false
> }
> [root@quasar-tvqwpy-1 /]# ls -lrt /tmp/testdata/
> total 8
> -rw-r--r-- 1 root root 4500 Apr  4 07:23 test {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]

Reply via email to