How to Quickly Check the Memory Used by Each Gluster Translator in a Statedump?
Issue
-
When a gluster process is consuming a lot of memory, a statedump is normally requested to analyze which gluster translator might be leaking. The steps to gather this information depend on the process for which the memory consumption is observed. Please, refer to the Gluster Administration Guide, section 19.8 for further information on how to obtain this data for the specific Gluster process affected.
-
Normally, a few statedumps are requested to compare how the memory usage grows. So please make sure to provide different statedumps when the resident set size of the concerning process increases significantly.
-
Once a statedump is collected, how to quickly check how much memory is used by each translator?
Environment
- Red Hat Gluster Storage 3.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
