Back to bug 1312812
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-02-29 10:00:29 UTC | Keywords | ZStream | |
| Prashanth Pai | 2016-02-29 10:02:19 UTC | Keywords | FutureFeature | |
| Blocks | 1299184 | |||
| Assignee | sankarshan | ppai | ||
| Doc Type | Bug Fix | Enhancement | ||
| SATHEESARAN | 2016-03-03 16:30:04 UTC | QA Contact | sasundar | sbhaloth |
| Rahul Hinduja | 2016-03-04 09:28:01 UTC | CC | rhinduja | |
| Rejy M Cyriac | 2016-03-08 07:48:09 UTC | CC | rcyriac | |
| Red Hat Bugzilla Rules Engine | 2016-03-08 08:16:22 UTC | Target Release | --- | RHGS 3.1.3 |
| Prashanth Pai | 2016-03-10 09:02:15 UTC | Priority | unspecified | medium |
| Blocks | 1299184 | 1311386 | ||
| Prashanth Pai | 2016-03-10 09:28:38 UTC | CC | thiago | |
| Prashanth Pai | 2016-03-17 06:04:41 UTC | Status | NEW | ASSIGNED |
| Prashanth Pai | 2016-04-07 06:54:57 UTC | Status | ASSIGNED | POST |
| Prashanth Pai | 2016-04-15 14:14:05 UTC | Status | POST | MODIFIED |
| Prashanth Pai | 2016-04-19 08:36:29 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | swiftonfile-2.3.0-1 | |||
| Prashanth Pai | 2016-04-19 12:06:48 UTC | Summary | gluster-swift: Object expiration feature needs separate volume and isn't scalable | [RHEL-7] gluster-swift: Object expiration feature needs separate volume and isn't scalable |
| Prashanth Pai | 2016-04-21 11:20:16 UTC | Fixed In Version | swiftonfile-2.3.0-1 | swiftonfile-2.3.0-2 |
| Prashanth Pai | 2016-04-25 07:23:26 UTC | Summary | [RHEL-7] gluster-swift: Object expiration feature needs separate volume and isn't scalable | [RHEL-7] gluster-swift: Object expiration feature does not scale well as object expirer daemon times out |
| Prashanth Pai | 2016-05-18 10:05:22 UTC | Doc Text | Feature: Improve object expiration feature by reducing chances of object expirer daemon timing out. Reason: As the number of zero-byte tracker objects in gsexpiring volume increases to millions in number, container server takes a lot of time to return the listing of objects to object expirer daemon. This causes object expirer daemon to timeout on the request sent to container server. Consequently, object expirer daemon cannot proceed with expiration of objects. Result: It is now less likely for object expirer daemon to timeout on request sent to container server. |
|
| surabhi | 2016-06-01 05:41:40 UTC | Status | ON_QA | VERIFIED |
| Anjana Suparna Sriram | 2016-06-16 05:43:18 UTC | CC | asriram | |
| Doc Text | Feature: Improve object expiration feature by reducing chances of object expirer daemon timing out. Reason: As the number of zero-byte tracker objects in gsexpiring volume increases to millions in number, container server takes a lot of time to return the listing of objects to object expirer daemon. This causes object expirer daemon to timeout on the request sent to container server. Consequently, object expirer daemon cannot proceed with expiration of objects. Result: It is now less likely for object expirer daemon to timeout on request sent to container server. | The Improve object expiration feature is enhanced by reducing chances of object expirer daemon timing out. Since the number of zero-byte tracker objects in gsexpiring volume increases to millions in number, container server takes a lot of time to return the listing of objects to object expirer daemon. This causes object expirer daemon to timeout on the request sent to container server. Consequently, object expirer daemon cannot proceed with expiration of objects. Hence, it is now less likely for object expirer daemon to timeout on request sent to container server. |
||
| errata-xmlrpc | 2016-06-23 00:56:01 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-06-23 05:31:14 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-06-23 01:31:14 UTC |
Back to bug 1312812