Back to bug 1023120
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Gowrishankar Rajaiyan | 2013-11-09 11:01:19 UTC | CC | grajaiya | |
| Susant Kumar Palai | 2014-01-12 18:07:48 UTC | CC | spalai | |
| Vivek Agarwal | 2014-01-28 08:35:25 UTC | CC | vagarwal | |
| Assignee | rhs-bugs | rgowdapp | ||
| krishnan parthasarathi | 2014-02-28 09:44:01 UTC | Component | glusterfs | gluster-quota |
| Sudhir D | 2014-08-22 09:29:10 UTC | QA Contact | sdharane | storage-qa-internal |
| Vijaikumar Mallikarjuna | 2015-01-09 07:16:20 UTC | Priority | unspecified | low |
| CC | vmallika | |||
| Vijaikumar Mallikarjuna | 2015-01-12 13:36:00 UTC | Status | NEW | CLOSED |
| 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:36:00 UTC | |||
| Vijaikumar Mallikarjuna | 2015-01-15 07:12:31 UTC | Status | CLOSED | NEW |
| Resolution | WONTFIX | --- | ||
| Keywords | Reopened | |||
| Vijaikumar Mallikarjuna | 2015-01-16 08:07:42 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:36:00 UTC | 2015-01-16 03:07:42 UTC | ||
| Pavithra | 2015-01-16 08:37:05 UTC | Depends On | 1182921 | |
| Rejy M Cyriac | 2016-09-17 12:40:24 UTC | CC | rhs-bugs, storage-qa-internal | |
| Component | gluster-quota | quota |
Back to bug 1023120