Bug 1337867

Summary: [nfs-ganesha]: tracker for nfs-ganesha memory consumption issue
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shashank Raj <sraj>
Component: nfs-ganeshaAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED CURRENTRELEASE QA Contact: Manisha Saini <msaini>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: bkunal, ffilz, jthottan, kkeithle, ndevos, olim, otira.fuu, rabhat, rcyriac, skoduri
Target Milestone: ---Keywords: Tracking, Triaged, ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-19 06:19:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1240172, 1282669, 1338068, 1351928, 1386635    
Bug Blocks: 1472361    

Description Shashank Raj 2016-05-20 09:53:15 UTC 
Description of problem:

Based on several customer reported issues and during qe testing, we found that the nfs-ganesha process consumes a lot of memory and can ultimately result in OOM kill issue, depending on the workload.

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

nfs-ganesha-2.3.1-7

How reproducible:

Always

Steps to Reproduce:

Running higher workloads could result in OOM kill of nfs-ganesha process.

Actual results:

Higher memory consumption by nfs-ganesha process and possible OOM kill.

Expected results:
 
Additional info:

The earlier tracking issue for this problem was (https://bugzilla.redhat.com/show_bug.cgi?id=1240172) which was contradicting with the title of that bug, so this new bug has been created to track the specific problem of ganesha memory consumption.