Back to bug 1026371
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Saurabh | 2013-11-07 13:42:08 UTC | CC | saujain | |
| Summary | quota: Soft limit not triggered after increasing quota size. | quota: Soft limit not triggered after increasing quota size and even after modifying soft-limit %age | ||
| Ben Turner | 2013-11-07 19:44:49 UTC | QA Contact | sdharane | bturner |
| Saurabh | 2013-12-11 04:48:50 UTC | Summary | quota: Soft limit not triggered after increasing quota size and even after modifying soft-limit %age | quota: Soft limit alert not triggered after increasing quota size and even after modifying soft-limit %age |
| Vivek Agarwal | 2014-01-28 08:40:55 UTC | Assignee | rhs-bugs | kparthas |
| krishnan parthasarathi | 2014-02-28 09:44:38 UTC | Component | glusterfs-server | gluster-quota |
| Vijay Bellur | 2015-01-09 06:54:01 UTC | Priority | unspecified | low |
| Vijaikumar Mallikarjuna | 2015-01-12 13:35:17 UTC | Status | NEW | CLOSED |
| CC | vmallika | |||
| Resolution | --- | WONTFIX | ||
| Doc Text | When the quota hard-timeout is set to default value of 30, the quota limit is checked once in 30 seconds and during that 30 second time window there is possibility of quota hard-limit being exceeded. In order to attain a strict checking of quota limit it is recommended to set the quota soft-timeout and hard-timeout to lower value so that quota limit is checked frequently, and possibility of quota hard-limit being exceeded is reduced. | |||
| Doc Type | Bug Fix | Known Issue | ||
| Last Closed | 2015-01-12 08:35:17 UTC | |||
| Vijaikumar Mallikarjuna | 2015-01-15 07:11:58 UTC | Status | CLOSED | NEW |
| Resolution | WONTFIX | --- | ||
| Keywords | Reopened | |||
| Vijaikumar Mallikarjuna | 2015-01-16 08:07:24 UTC | Keywords | Reopened | |
| Status | NEW | CLOSED | ||
| Depends On | 1182890 | |||
| Resolution | --- | WONTFIX | ||
| Doc Text | When the quota hard-timeout is set to default value of 30, the quota limit is checked once in 30 seconds and during that 30 second time window there is possibility of quota hard-limit being exceeded. In order to attain a strict checking of quota limit it is recommended to set the quota soft-timeout and hard-timeout to lower value so that quota limit is checked frequently, and possibility of quota hard-limit being exceeded is reduced. | Expected 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 | ||
| Last Closed | 2015-01-12 08:35:17 UTC | 2015-01-16 03:07:24 UTC | ||
| Pavithra | 2015-01-16 08:37:05 UTC | Depends On | 1182921 | |
| John Skeoch | 2015-11-03 23:05:55 UTC | CC | nsathyan | |
| Rejy M Cyriac | 2016-09-17 12:43:28 UTC | CC | rhs-bugs, storage-qa-internal | |
| Component | gluster-quota | quota |
Back to bug 1026371