Comment 15Bala Konda Reddy M
2018-05-14 13:18:36 UTC
Build: 3.12.2-9
Followed the steps.
1. On an 8 node setup, created 200 volumes(100EC and 100 Replicate) volumes.
2. Noted down glusterd memory as 94MB and ran gluster get-state detail for 17000 times in a loop in the background.
3. Executed gluster vol status for 1000 times on one of the nodes in a loop
4. The glusterd memory increased by 220MB.
With the scale of volumes considered and continuously executing vol status. This increase is acceptable.
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