Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1522833 - high memory usage by glusterd on executing gluster volume set operations [NEEDINFO]
high memory usage by glusterd on executing gluster volume set operations
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
3.2
Unspecified Unspecified
urgent Severity unspecified
: ---
: RHGS 3.4.0
Assigned To: Mohit Agrawal
Bala Konda Reddy M
:
Depends On:
Blocks: 1503138 1526363 1527551
  Show dependency treegraph
 
Reported: 2017-12-06 09:32 EST by Raghavendra Bhat
Modified: 2018-09-04 02:42 EDT (History)
7 users (show)

See Also:
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 02:40:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
amukherj: needinfo? (rabhat)
amukherj: needinfo? (moagrawa)


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2607 None None None 2018-09-04 02:42 EDT

  None (edit)
Comment 13 Bala Konda Reddy M 2018-04-19 07:32:19 EDT
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
Comment 15 errata-xmlrpc 2018-09-04 02:40:20 EDT
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

Note You need to log in before you can comment on or make changes to this bug.