[Gluster-devel] Potential Memory Leak?

[Krishna Srinivas]

Hi Karl,

Your glusterfsd config is simple with only 4 translators.

Is the problem seen every time you run your script?

Can you run the script using a simpler client config file? just
connect the client to a single server (no afr/unify etc on the
client side)

just have the folloing in your client spec and see if the glusterfsd
memory grows:

---

volume sxx04
 type protocol/client
 option transport-type tcp/client
 option remote-host sxx04b
 option remote-subvolume brick
end-volume

----



On 10/23/07, Karl Bernard <karl at vomba.com> wrote:
> Hello Krishna,
>
> I have 5 servers running the client and 4 servers running the brick
> server. In the config I was testing, only 3 of the brick servers are used.
>
> I have scripts running on the 5 servers that open images of 5k to 20k
> and create thumbnails for those images of about 4k. All files are
> written in a hash directory structure.
>
> After reading and creating a lot of files (1 million for example),  I
> can see that the memory usage for the glusterfsd have grown substancially.
>
> Software versions:
> glusterfs-1.3.4
> fuse-2.7.0-glfs4
>
> <<-- glusterfs-server.vol -->>
> volume brick-posix
>         type storage/posix
>         option directory /data/glusterfs/dataspace
> end-volume
>
> volume brick-ns
>         type storage/posix
>         option directory /data/glusterfs/namespace
> end-volume
>
> volume brick
>   type performance/io-threads
>   option thread-count 2
>   option cache-size 32MB
>   subvolumes brick-posix
> end-volume
>
> volume server
>         type protocol/server
>         option transport-type tcp/server
>         subvolumes brick brick-ns
>         option auth.ip.brick.allow 172.16.93.*
>         option auth.ip.brick-ns.allow 172.16.93.*
> end-volume
> <<-- end of glusterfs-server.vol -->>
>
> <<-- start client.sharedbig.vol -->>
> volume sxx01-ns
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host sxx01b
>  option remote-subvolume brick-ns
> end-volume
>
> volume sxx02-ns
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host sxx02b
>  option remote-subvolume brick-ns
> end-volume
>
> volume sxx03-ns
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host sxx03b
>  option remote-subvolume brick-ns
> end-volume
>
> volume sxx04-ns
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host sxx04b
>  option remote-subvolume brick-ns
> end-volume
>
> volume sxx01
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host sxx01b
>  option remote-subvolume brick
> end-volume
>
> volume sxx02
>  type protocol/client
>  option transport-type tcp/client
>  option remote-host sxx02b
>  option remote-subvolume brick
> end-volume
>