If you don't use it - just disable it.
Such memory usage indicates memory leak, so it's worth tesring on latest Gluster version and opening a github issue if persists.
Best Regards,
Strahil Nikolov
On Tue, May 24, 2022 at 0:16, Ingo Fischer<ingo@xxxxxxxxxxxxx> wrote:Hi,while checking some stuff on my glusterfs cluster I noticed on somemachines that glustereventsd took 2-5GB of RAM! On some other nodes itused near to no RAM.In fact there are no webhooks registered at all when I call the statuscommand ... So whats that thing doing and why it is eating up RAM?Does anyone else see something like this?I'm on glusterfs 9.5.I only use gstatus to query the status in the monitoring ... thats all.When now thinking I also consider simply disabling the service because Ido not use it at all ... so, is there any need of it when notregistering webhooks to get events from the cluster? is there any adviceor best practices?Thank you for your information and thoughts.Ingo________Community Meeting Calendar:Schedule -Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTCGluster-users mailing list
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
