<div class="gmail_quote"><div>Did you do 'gluster volume set' or multiple add-brick operations on the volume?</div><div><br></div><div>Also, you can do 'kill -USR1 <PID>' to get details on what would be consuming memory (check /tmp/glusterdump.<PID> after kill).</div>
<div><br></div><div>Again, please share the information on which version of glusterfs you are using, that helps to see if we had any known leaks in that particular version.</div><div><br></div><div>Regards,</div><div>Amar</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Memory consumpsion on server 1:<br>
29256 glusterfs --volume-name=vmail /kit/vmail1<br>
52968 glusterfs --volume-name=global /kit/global<br>
166860 /usr/sbin/glusterfsd -p /var/run/glusterfsd.pid -f /etc/glusterfs/glusterfsd.vol --log-file /var/log/glusterfs/glusterfsd.<u></u>vol.log<br>
2101844 glusterfs --volume-name=data /kit/data1<br>
<br>
Memory consumpsion on server 2:<br>
132784 glusterfs --volume-name=global /kit/global<br>
196996 /usr/sbin/glusterfsd -p /var/run/glusterfsd.pid -f /etc/glusterfs/glusterfsd.vol --log-file /var/log/glusterfs/glusterfsd.<u></u>vol.log<br>
557648 glusterfs --volume-name=vmail /kit/vmail1<br>
1586040 glusterfs --volume-name=data /kit/data1<br>
<br>
------</blockquote></div>