Back to bug 1019752
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Vijaykumar Koppad | 2013-10-16 11:41:08 UTC | Summary | [Quota] quota failes generate alerts on the slave in a geo-rep setup even after slave has crossed soft-limit | [Quota] quota fails generate alerts on the slave in a geo-rep setup even after slave has crossed soft-limit |
| Vijaykumar Koppad | 2013-10-16 11:41:25 UTC | Summary | [Quota] quota fails generate alerts on the slave in a geo-rep setup even after slave has crossed soft-limit | [Quota] quota fails to generate alerts on the slave in a geo-rep setup even after slave has crossed soft-limit |
| Vijaykumar Koppad | 2013-10-16 13:06:36 UTC | Summary | [Quota] quota fails to generate alerts on the slave in a geo-rep setup even after slave has crossed soft-limit | [Quota] quota failes generate alerts on the slave in a geo-rep setup even after slave has crossed soft-limit |
| Gowrishankar Rajaiyan | 2013-10-16 13:08:51 UTC | Keywords | ZStream | |
| CC | grajaiya | |||
| Vivek Agarwal | 2013-10-17 06:55:50 UTC | CC | vagarwal | |
| Vivek Agarwal | 2013-11-25 09:13:49 UTC | Priority | unspecified | medium |
| Vivek Agarwal | 2014-01-28 08:40:54 UTC | Assignee | rhs-bugs | kparthas |
| krishnan parthasarathi | 2014-02-28 09:44:10 UTC | Component | glusterfs-server | gluster-quota |
| Sudhir D | 2014-08-22 09:27:11 UTC | QA Contact | sdharane | storage-qa-internal |
| John Skeoch | 2014-08-25 00:50:57 UTC | CC | bbandari | |
| John Skeoch | 2014-11-09 22:59:25 UTC | CC | bbandari | david.macdonald |
| Vijaikumar Mallikarjuna | 2015-01-12 13:39:48 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:39:48 UTC | |||
| Vijaikumar Mallikarjuna | 2015-01-15 07:13:49 UTC | Status | CLOSED | NEW |
| Resolution | WONTFIX | --- | ||
| Keywords | Reopened | |||
| Vijaikumar Mallikarjuna | 2015-01-16 08:09:06 UTC | Keywords | Reopened, ZStream | |
| 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:39:48 UTC | 2015-01-16 03:09:06 UTC | ||
| Pavithra | 2015-01-16 08:37:05 UTC | Depends On | 1182921 | |
| John Skeoch | 2015-11-03 23:05:42 UTC | CC | nsathyan | |
| Rejy M Cyriac | 2016-09-17 12:36:42 UTC | CC | rhs-bugs, storage-qa-internal | |
| Component | gluster-quota | quota |
Back to bug 1019752