Bug 802002

Summary:	Established connnections keep increasing during graph change
Product:	[Community] GlusterFS	Reporter:	Anush Shetty <ashetty>
Component:	fuse	Assignee:	Raghavendra G <rgowdapp>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-10 08:39:45 UTC	Type:	---
Regression:	---	Mount Type:	fuse
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Anush Shetty 2012-03-10 06:48:16 UTC

Description of problem: While doing volume set in a loop to trigger graph change, the number of established connections for the glusterfs client process keep increasing exponentially 


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


How reproducible: Consistently


Steps to Reproduce:
1. netstat -np

Comment 1 Amar Tumballi 2012-03-25 07:14:27 UTC

Check if its already fixed.

Comment 2 Anush Shetty 2012-03-26 05:04:24 UTC

Still seen in the mainline/3.3.0qa31

Comment 3 Raghavendra G 2012-04-03 03:36:58 UTC

After a graph-switch, atleast one request should be sent to /dev/fuse. Without it, fuse-bridge cannot initiate cleanup. Can you check whether this issue exists even with an operation like ls b/w graph switches?

Comment 4 Raghavendra G 2012-04-10 08:39:45 UTC

Closing this bug, since with operations on mountpoint, cleanup is done.