Bug 1182890

Summary: Quota: soft-timeout and hard-timeout of quota - expected behavior
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vijaikumar Mallikarjuna <vmallika>
Component: doc-Administration_GuideAssignee: storage-doc
doc-Administration_Guide sub component: Default QA Contact: storage-qa-internal <storage-qa-internal>
Status: CLOSED NOTABUG Docs Contact:
Severity: medium    
Priority: unspecified CC: asriram, bmohanra, mhideo, nlevinki, psriniva, rhs-bugs, rwheeler, smohan, storage-doc
Version: 2.1   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1182921 (view as bug list) Environment:
Last Closed: 2015-01-22 10:07:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 999458, 1001548, 1019752, 1020275, 1023120, 1026371, 1116115, 1116121, 1182921    

Description Vijaikumar Mallikarjuna 2015-01-16 07:16:01 UTC 
Currently below mentioned bugs are marked as known issues. Actually they are expected behavior of quota.

Bug# 1026371 - quota: Soft limit alert not triggered after increasing quota size and even after modifying soft-limit %age
Bug# 1023120 - Appending data to a file using Vi editor violates quota limits
Bug# 1020275 - quota: Exceeding upto 100% of the hard limit on file creation with different sizes and quota limit is less than 2GB.
Bug# 1019752 - [Quota] quota fails generate alerts on the slave in a geo-rep setup even after slave has crossed soft-limit
Bug# 1116121 - Quota: Soft limits are not triggered when the hard limit is exceeded.
Bug# 1116115 - Quota: Smaller limits getting crossed by as much as 300%
Bug# 999458 - quota: limit gets crossed for small values of "hard limit" setting
Bug# 1001548 - quota: disk quota was set to 1.0GB but could create a file of 1.4GB from mount.



Here is the behavior of quota:
If the rate of I/O is more than the value of hard-timeout and soft-timeout, there is possibility of quota limit being exceeded
For example:

If the rate of IO is 1GB/sec
If hard-timeout is set to 5sec (default value).
If soft-timeout is set to 60sec (default value).

Then we may exceed quota limit by ~30GB - 60GB

In order to attain a strict checking of quota limit, then you need to lower the value of hard-timeout and soft-timeout
Command to set timeout:
gluster volume quota <volume-name> soft-timeout 0
gluster volume quota <volume-name> hard-timeout 0
Comment 2 Bhavana 2015-01-22 10:07:11 UTC 
Hi Vijai,


I found that the information suggested by you is already present in the Admin guide that is added as a note under section 13.5.

https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/ch13s05.html

Based on our discussion this information is sufficient and hence closing this bug.