You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 9, 2024. It is now read-only.
The memory leak is caused by running "gluster volume status all" thousands of times which is the similar behavior with gluster-exporter does.
This issue has been fixed in glusterfs-3.8
My experience with glusterfs-3.6.9, the exporter will cause the severe memory leak on the server.
(prometheus scrape period : 180s)
The glusterd will crashed from time to time due to out of memory.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Here is a memory leak issue of glusterd reported in 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1287517
The memory leak is caused by running "gluster volume status all" thousands of times which is the similar behavior with gluster-exporter does.
This issue has been fixed in glusterfs-3.8
My experience with glusterfs-3.6.9, the exporter will cause the severe memory leak on the server.
(prometheus scrape period : 180s)
The glusterd will crashed from time to time due to out of memory.
The text was updated successfully, but these errors were encountered: