[Bugs] [Bug 1751014] Memory leak when often run gluster volume status

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1751014

Sanju <srakonde at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |srakonde at redhat.com
              Flags|                            |needinfo?(padner2002 at list.r
                   |                            |u)



--- Comment #4 from Sanju <srakonde at redhat.com> ---
Hi,

I see the increase in memory of gf_common_mt_txn_opinfo_obj_t structure, which
has been fixed in release-6. Can you please check whether your cluster is
running at appropriate op-version? With the above-mentioned fix, the memory
leak has greatly reduced.

[mgmt/glusterd.management - usage-type gf_common_mt_txn_opinfo_obj_t memusage] 
 |  [mgmt/glusterd.management - usage-type gf_common_mt_txn_opinfo_obj_t
memusage]
  size=610288                                                                  
 |  size=1427664                                                                
  num_allocs=5449                                                              
 |  num_allocs=12747                                                            
  max_size=610400                                                              
 |  max_size=1427776                                                            
  max_num_allocs=5450                                                          
 |  max_num_allocs=12748                                                        
  total_allocs=22184                                                           
 |  total_allocs=51138            

Also, I tried running gluster volume status in loop for 1000 times and I don't
see the leak in gf_common_mt_txn_opinfo_obj_t. Please get back with output of
"gluster v get all cluster.op-version".

Thanks,
Sanju

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.