Bug 1471681

Summary: Steadily high CPU usage
Product: [Retired] nfs-ganesha Reporter: Jiri Lunacek <jiri.lunacek>
Component: FSAL_GLUSTERAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: jthottan, renaud.fortier, rhs-bugs, rik.theys, storage-qa-internal
Target Milestone: ---   
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-09-24 14:42: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:

Description Jiri Lunacek 2017-07-17 09:05:08 UTC 
Description of problem:
Each ganesha export with FSAL_GLUSTER consumes 3-10% CPU.

I have just found these two notions of this issue on the internet with no solution yet.
http://lists.gluster.org/pipermail/gluster-users.old/2016-November/028939.html
https://github.com/nfs-ganesha/nfs-ganesha/issues/124


Version-Release number of selected component (if applicable):
nfs-ganesha-2.3.3-1.el7.x86_64
nfs-ganesha-gluster-2.3.3-1.el7.x86_64
glusterfs-ganesha-3.8.13-1.el7.x86_64


Steps to Reproduce:
1. Create a gluster volume, disable gnfs
2. Create ganesha configuration
3. Start nfs-ganesha service
4. Observe a thread which is consuming CPU

Additional info:
Sample export config:
EXPORT{
	Export_Id= 19 ;
	Path = "/clientmounts/replicated/test";
	FSAL {
		name = GLUSTER;
		hostname="localhost";
		volume="storage-replicated";
		volpath="/clientmounts/test";
	}
	Access_type = RW;
	Disable_ACL = true;
	Squash="No_root_squash";
	Pseudo="/clientmounts/replicated/test";
	Protocols = "3", "4" ;
	Transports = "UDP","TCP";
	SecType = "sys";
}
Comment 3 renaud.fortier 2017-08-24 14:07:45 UTC 
We have the same problem with nfs-ganesha 2.5.1
Comment 4 Jiffin 2018-09-24 08:35:10 UTC 
(In reply to renaud.fortier from comment #3)
> We have the same problem with nfs-ganesha 2.5.1

Can u try with latest ganesha. IMO we resolved this issue on current nfs-ganesha
Comment 5 renaud.fortier 2018-09-24 13:11:45 UTC 
Indeed! the issue is solved with the latest version. 
Thanks.
Comment 6 Jiffin 2018-09-24 14:42:24 UTC 
Thanks closing this bug as fixed in nfs-ganesha 2.6