<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 14pt; color: #000000'>Hi all, <div>I am looking into this issue, but could not make much from the statedumps.</div><div>I will try to reproduce this issue. If i know what kind of operations (reads, writes, metadata r/ws, etc) are being done,</div><div>and if there are any other configuration changes w.r.t GlusterFS, it'll be of great help.<br><br><div><span name="x"></span>Regards,<br>Rajesh Amaravathi,<br>Software Engineer, GlusterFS<br>RedHat Inc.<span name="x"></span><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Xavier Normand" <xavier.normand@gmail.com><br><b>To: </b>"Philip Poten" <philip.poten@gmail.com><br><b>Cc: </b>gluster-users@gluster.org<br><b>Sent: </b>Tuesday, June 12, 2012 6:32:41 PM<br><b>Subject: </b>Re: [Gluster-users] Memory leak with glusterfs NFS on 3.2.6<br><br>Hi Philip,<div><br></div><div>I do have about the same problem that you describe. There is my setup:</div><div><br></div><div>Gluster: Two bricks running gluster 3.2.6</div><div><br></div><div>Clients:</div><div>4 clients running native gluster fuse client.</div><div>2 clients running nfs client</div><div><br></div><div>My nfs client are not doing that much traffic but i was able to view after a couple days that the brick used to mount the nfs is having memory issue.</div><div><br></div><div>i can provide more info as needed to help correct the problem.</div><div><br></div><div>Thank's</div><div><br></div><div>Xavier</div><div><br></div><div><img height="427" width="501" id="78a75a38-371b-4ee6-a9b6-70accdb60cc6" src="cid:38664A7C-732E-4B64-AFF3-13FFDB09C17B@ldm.local"></div><div><br></div><div><br></div><div><div><div>Le 2012-06-12 à 08:18, Philip Poten a écrit :</div><br class="Apple-interchange-newline"><blockquote><div>2012/6/12 Dan Bretherton <<a href="mailto:d.a.bretherton@reading.ac.uk" target="_blank">d.a.bretherton@reading.ac.uk</a>>:<br><blockquote>I wonder if this memory leak is the cause of the NFS performance degradation<br></blockquote><blockquote>I reported in April.<br></blockquote><br>That's probable, since the performance does go down for us too when<br>the glusterfs process reaches a large percentage of RAM. My initial<br>guess was that it's the file system cache that's being eradicated,<br>thus iowait increases. But a closer look at our munin graphs implies,<br>that it's also the user space that eats more and more CPU<br>proportionally with RAM:<br><br><a href="http://imgur.com/a/8YfhQ" target="_blank">http://imgur.com/a/8YfhQ</a><br><br>There are two restarts of the whole gluster process family visible on<br>those graphs: one a week ago at the very beginning (white in the<br>memory graph, as munin couldn't fork all it needed), and one<br>yesterday. The drop between 8 and 9 was due to a problemv unrelated to<br>gluster.<br><br>Pranith: I just made one dump, tomorrow I'll make one more and mail<br>them both to you so that you can compare them. While I just restarted<br>yesterday, the leak should be visible, as the process grows a few<br>hundred MB every day.<br><br>thanks for the fast reply,<br>Philip<br>_______________________________________________<br>Gluster-users mailing list<br>Gluster-users@gluster.org<br>http://gluster.org/cgi-bin/mailman/listinfo/gluster-users<br></div></blockquote></div><br></div><br>_______________________________________________<br>Gluster-users mailing list<br>Gluster-users@gluster.org<br>http://gluster.org/cgi-bin/mailman/listinfo/gluster-users<br></div><br></div></div></body></html>