Bug 1522833
| Summary: | high memory usage by glusterd on executing gluster volume set operations | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Raghavendra Bhat <rabhat> | |
| Component: | glusterd | Assignee: | Mohit Agrawal <moagrawa> | |
| Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | rhgs-3.2 | CC: | amukherj, moagrawa, rabhat, rhinduja, rhs-bugs, storage-qa-internal, vbellur | |
| Target Milestone: | --- | |||
| Target Release: | RHGS 3.4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.12.2-2 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1526363 (view as bug list) | Environment: | ||
| Last Closed: | 2018-09-04 06:40:20 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: | 1503138, 1526363, 1527551 | |||
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2607 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Build : 3.12.2-7 On brick mux enabled setup. Created 100 volumes of volume type replicate(2X3) and checked the glusterd memory,73 MB. Set the following volume option for all the volumes in a loop. for i in {1..100};do gluster v set 2cross3_$i cluster.self-heal-daemon off;sleep 3 ;gluster v set 2cross3_$i group metadata-cache;sleep 3;gluster v set 2cross3_$i cluster.lookup-optimize on;sleep 3 ;done After setting the volume options, glusterd memory increased by 14 MB, 87MB. As there isn't any drastic increase in memory while setting volume set operations. Hence marking it as verified