Bug 2155171 - Excessive memory consumption on gluster fuse
Summary: Excessive memory consumption on gluster fuse
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: fuse
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Csaba Henk
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-20 09:46 UTC by Rafrojas
Modified: 2023-01-17 05:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-17 05:56:40 UTC
Embargoed:


Attachments (Terms of Use)

Description Rafrojas 2022-12-20 09:46:06 UTC
Before you record your issue, ensure you are using the latest version of Gluster.


Provide version-Release number of selected component (if applicable):
OCS 3.11
 
Have you searched the Bugzilla archives for same/similar issues reported.
Yes, find similar issue, but need confirmation if applicable BZ#1749168

Did you run SoS report with Insights tool?.

Have you discovered any workarounds?. 
If not, Read the troubleshooting documentation to help solve your issue.
(https://mojo.redhat.com/groups/gss-gluster (Gluster feature and its troubleshooting)  https://access.redhat.com/articles/1365073 
(Specific debug data that needs to be collected for GlusterFS to help troubleshooting)

Please provide the below Mandatory Information:
1 - gluster v <volname> info
2 - gluster v <volname> heal info
3 - gluster v <volname> status
4 - Fuse Mount/SMB/nfs-ganesha/OCS ???



Describe the issue:(please be detailed as possible and provide log snippets)
[Provide TimeStamp when the issue is seen]

We are experiencing excessive memory consumption on some cluster nodes, related with gluster fuse .


Is this issue reproducible? If yes, share more details.:
The consumption is stable at high level


Steps to Reproduce:
1.
2.
3.
Actual results:
 
Expected results:
 
Any Additional info:


Note You need to log in before you can comment on or make changes to this bug.