[Gluster-devel] glusterfs-3.5.0beta4 released

Vijay Bellur vbellur at redhat.com
Tue Apr 1 05:20:08 UTC 2014


On 03/27/2014 01:44 PM, Emmanuel Dreyfus wrote:
> On Mon, Mar 17, 2014 at 04:29:29PM +0530, Vijay Bellur wrote:
>>> [protocol/server.gfs35b4-server - usage-type 48 memusage]
>>> size=251598236
>>> num_allocs=5885242
>>> max_size=251598236
>>> max_num_allocs=5885242
>>> total_allocs=8755572
>>>
>>
>> Can you please try with the latest release-3.5 code? In my testing (untar +
>> rm -rf ) does not cause memory leaks after [1] was merged.
>
> Here are results with release-3.5: My test comletes, but glusterfs brick
> processes eat up to 2.8 GB at the end.
>
> Here is the dump for a 1.3 GB glusterfsd:
> http://ftp.espci.fr/shadow/manu/export-wd2a.24974.dump.1395821561
>
> Worst offenders by decreasing order or num_allocs * max_size:
>
> [protocol/server.gfs35branch-server - usage-type 17 memusage]
> size=4940760
> num_allocs=18715
> max_size=5363424
> max_num_allocs=20316
> total_allocs=49280206
>
> [features/locks.gfs35branch-locks - usage-type 107 memusage]
> size=747252
> num_allocs=16983
> max_size=1050456
> max_num_allocs=23874
> total_allocs=210769
>
> [features/locks.gfs35branch-locks - usage-type 108 memusage]
> size=1273860
> num_allocs=15165
> max_size=1399524
> max_num_allocs=16661
> total_allocs=149491
>
> [features/locks.gfs35branch-locks - usage-type 40 memusage]
> size=529280
> num_allocs=16983
> max_size=704317
> max_num_allocs=23879
> total_allocs=70930525
>
> [features/locks.gfs35branch-locks - usage-type 107 memusage]
> size=747252
> num_allocs=16983
> max_size=1050456
> max_num_allocs=23874
> total_allocs=210769
>
> [debug/io-stats./export/wd2a - usage-type 109 memusage]
> size=538080
> num_allocs=3852
> max_size=1423300
> max_num_allocs=10175
> total_allocs=75457
>
>


Does look like most of the memory consumption in here is coming from 
inode_ctx allocations across translators. This certainly seems to point 
towards a missing inode_unref().

I assume that you have eager locks set to off by default in your 
testing. Apart from this, are there other volume configuration changes?

Thanks,
Vijay




More information about the Gluster-devel mailing list