Bug 1163709

Summary:	gstatus: If a volume is mounted more than once from a machine, it is still considered as a single client
Product:	[Community] GlusterFS	Reporter:	Sachidananda Urs <surs>
Component:	unclassified	Assignee:	Paul Cuzner <pcuzner>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, surs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-09 13:59:37 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 Sachidananda Urs 2014-11-13 10:32:42 UTC

If a volume is mounted many times from a single client, every mount should be considered a client to the volume.

i.e if there are 4 `glusterfs' processes, they should still be considered 4 clients. Currently the number of clients is shown as 1.

Gluster Clients : 1

Comment 1 Paul Cuzner 2014-11-14 22:02:31 UTC

Yes this is how it works. the clients list is added to a python set, so only unique client IP's remain. The idea was to provide admins with a view of how many client machines are connected to volume/cluster - basically so they can understand the environment i.e. 4 node rhs cluster supports 100 client machines.

If I don't do this, one physical client will shows as n connections so the admin has no idea how many 'real' clients the rhs cluster is supporting.

Make sense?

Comment 2 Niels de Vos 2014-11-18 12:34:43 UTC

Can be closed as NOTABUG?

Comment 3 Sachidananda Urs 2014-12-09 13:59:37 UTC

Cool. Can be closed. I'm closing it.