Red Hat Bugzilla – Bug 1522833
high memory usage by glusterd on executing gluster volume set operations
Last modified: 2018-09-04 02:42:11 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
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