Description of problem:
We have moved to newer implementation of mem-pools. But statedump doesn't print the information about them. Github issue  captures upstream effort on this. But preliminary reading shows the work still has some parts to be completed. So, the effort includes:
* backporting https://review.gluster.org/18076
* reviewing whether the information printed by above patch is complete from the perspective of debugging memory consumption issues.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Patch is already available upstream.
(In reply to Amar Tumballi from comment #4)
> Patch is already available upstream.
If you are speaking about https://review.gluster.org/18076, we still need to evaluate whether it covers all aspects of newer memory pools. So, the work may not be complete
https://review.gluster.org/#/c/glusterfs/+/18075/ is needed too.
commit msg of one of patches  say - This only captures the information from 'struct mem_pool', and not from the global 'struct mem_pool_shared' or the pool_sweeper thread. The current details help with detecting memory leaks.
so we need to find out what is left out if we don't dump those fields and preferably add those two fields if important.
Based on the points discussed in #comment28,#comment30 and #comment31 , moving this bug to verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.