Bug 1653225

Description of problem:
=======================
on a brick mux setup, when we create volumes in sequence the glusterfsd memory also keeps increasing, but when we delete the volume, the memory is not getting freed up.
This can keep piling up if we do multiple volumes creates and deletes.



Version-Release number of selected component (if applicable):
=============
3.12.2-29

How reproducible:
==============
always

Steps to Reproduce:
1.create a brick mux setup
2.create a volume say basevol
3.now creating multiple volumes and also delete them(don't delete basevol), it can be seen that the brick mem footprint only keeps increasing and never decreases.


Actual results:
===========


Expected results:
===============
memory should be freed up after every volume delete

Additional info:
================
this issue was already reported and fixed as part of BZ#1535281 
However the problem has appeared again as part of a regression introduced sometime in 3.4.x

Raising this bug to track the above issue