Hi All, We are using GlusterFS 3.10.2 (upgraded from 3.7.0 last week) on CentOS 7.x . We continue to see memory utilization going up once every 3 days. The memory utilization of the server demon(glusterd) in ?server is keep on increasing. In about 30+ hours the Memory utilization of glusterd service alone will reach 70% of memory available. Since we have alarms for this threshold, we get notified and only way to stop it so far is to restart the glusterd.? The GlusterFS is configured in the two server nodes with replica option. Kindly let us know how to fix this memory leakage. Thanks in advance, Shridhar S N -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170623/8c0d47c7/attachment.html>
Mohammed Rafi K C
2017-Jul-27 13:53 UTC
[Gluster-users] Memory Leakage in Gluster 3.10.2-1
Are you still facing the problem ? If so, Can you please provide the workload , cmd_log_history file, log files , etc ? Regards Rafi KC On 06/23/2017 02:06 PM, shridhar s n wrote:> Hi All, > > We are using GlusterFS 3.10.2 (upgraded from 3.7.0 last week) on > CentOS 7.x . > > We continue to see memory utilization going up once every 3 days. The > memory utilization of the server demon(glusterd) in server is keep on > increasing. In about 30+ hours the Memory utilization of glusterd > service alone will reach 70% of memory available. Since we have alarms > for this threshold, we get notified and only way to stop it so far is > to restart the glusterd. > > The GlusterFS is configured in the two server nodes with replica option. > > Kindly let us know how to fix this memory leakage. > > Thanks in advance, > > Shridhar S N > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170727/ac60d3f2/attachment.html>
Reasonably Related Threads
- Memory Leakage in Gluster 3.10.2-1
- lpcSize
- NT_STATUS_NO_TRUST_SAM_ACCOUNT after temporary connectivity break to AD DC
- NT_STATUS_NO_TRUST_SAM_ACCOUNT after temporary connectivity break to AD DC
- Anyone knows how microsoft AEC can deal with mismatches between clocks of capture and render streams?